Comments

List the comments of an SEO planner action

seo_planner.comments.list

Lists the internal comments of an SEO Planner action, oldest first, paginated by cursor: content (sanitized HTML), author and mentioned member uids. 404 seo_item_not_found if the action does not exist in this organization. Requires view access to the SEO Planner.

Scope

seo_planner:read

Permission

View the module

MCP tool

seo_planner_comments_listOn the full surface; on the compact one, mb_execute_operation with id: "seo_planner.comments.list".

Declared cost: up to 203 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Comment on an SEO planner action

seo_planner.comments.create

Adds an internal comment to an SEO Planner action (simple HTML or text, sanitized; up to 10,000 characters) and bumps its comment_count. mentions are member uids to notify in the bell (only members of this organization or of its agency workspace receive the notice). The client portal does not show these comments. Returns the comment. Requires full access to the SEO Planner.

Scope

seo_planner:write

Permission

Edit in the module

MCP tool

seo_planner_comments_createOn the full surface; on the compact one, mb_execute_operation with id: "seo_planner.comments.create".

Declared cost: up to 3 reads and 2 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "content": "CONTENT"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "content": "CONTENT"
}'

Edit a comment of an SEO planner action

seo_planner.comments.update

Replaces the content (and mentions) of a comment on an SEO Planner action. Only its author can edit it (403 comment_author_only); only newly added mentions are notified. Returns the updated comment. Requires full access to the SEO Planner.

Scope

seo_planner:write

Permission

Edit in the module

MCP tool

seo_planner_comments_updateOn the full surface; on the compact one, mb_execute_operation with id: "seo_planner.comments.update".

Declared cost: up to 4 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "content": "CONTENT"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "content": "CONTENT"
}'

Delete a comment of an SEO planner action

seo_planner.comments.delete

Deletes a comment of an SEO Planner action and lowers its comment_count. Its author or an owner/admin of the organization can delete it (403 comment_delete_denied otherwise). It stays 30 days in the trash (platform.trash.restore brings it back to its action). Outside the app it needs a dry run and a confirm_token, except a REST DELETE with a key allowed to delete. Requires full access to the SEO Planner.

With an API key, this DELETE runs directly: the record stays 30 days in the trash and the response carries its trash_item_id. With an OAuth token, and through the MCP, it needs dry_run → confirm_token.

Scope

seo_planner:write and “Allow deletions” (seo_planner:delete in OAuth)

Permission

Edit in the module

MCP tool

seo_planner_comments_deleteOn the full surface; on the compact one, mb_execute_operation with id: "seo_planner.comments.delete".

Declared cost: up to 2 reads and 2 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X DELETE "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"