Lists the actions (cards) of the organization's SEO Planner, paginated by cursor (limit up to 200). Pass month_key (YYYY-MM) for the actions of one month, as the planner shows them, or from_month/to_month (inclusive) for a range of months; without a month filter, every action in chronological order. Optional filters: status (pending, in_progress, completed) and type. source_key returns the action created with that key (seo_planner.items.create): an exact match, normally one action, in id order, with the other filters applied to it; it reads only what matches, so it is the cheap way to check whether an action of yours already exists. A filter the query cannot apply (type; status together with a month) is applied while reading, and the page keeps reading until it has limit actions or has looked at 1,000 (then has_more is true and next_cursor continues where it stopped). Each action carries its month, status, type, sub-actions (checklist), content brief, backlink details, the pack or template it came from, its source_key if it was created with one, comment_count (0 when it has none) and who created it (created_by, with the person's current name). Errors: 400 month_filter_conflict (month_key with from_month/to_month), invalid_month_range, invalid_input. Requires view access to the SEO Planner.
Escopo
seo_planner:read
Permissão
Ver o módulo
Tool do MCP
seo_planner_items_listNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.list".
Custo declarado: até 1003 leituras e 0 escritas por chamada (contam na cota diária).
Parâmetros
limitintegerqueryopcional
How many items this page brings at most (see the maximum and the default in the schema).
Padrão: 50
cursorstringqueryopcional
The next_cursor of the previous page, exactly as it came (only for the same list and filters); without it, the first page.
month_keystringqueryopcional
Only the actions of this month (YYYY-MM), in the planner's order. Not together with from_month/to_month.
from_monthstringqueryopcional
From this month on (YYYY-MM, inclusive).
to_monthstringqueryopcional
Up to this month (YYYY-MM, inclusive).
statusenumqueryopcional
Only actions in this status: pending, in_progress or completed.
Only the action created with this source_key (exact match; normally one, since a key is unique in the organization). The other filters still apply to it.
Returns one action of the SEO Planner: title, subtitle, description, type, status, month (month_key YYYY-MM), sub-actions with their completed flag, content brief, backlink details, pack or template of origin, its source_key if it was created with one, comment_count and who created it. 404 seo_item_not_found if it does not exist in this organization. Requires view access to the SEO Planner.
Escopo
seo_planner:read
Permissão
Ver o módulo
Tool do MCP
seo_planner_items_getNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.get".
Custo declarado: até 1 leituras e 0 escritas por chamada (contam na cota diária).
Parâmetros
item_idstringrotaobrigatório
The action id (id of an item of seo_planner.items.list).
Resposta
idstring
titlestring
typestring
Action type (blog_post, on_page_seo, technical_seo…).
statusstring
pending, in_progress or completed.
comment_countnumber
Comments on the action (seo_planner.comments.list); 0 when it has none.
created_atnumber
updated_atnumber
organization_idstring | null
The organization the action belongs to.
subtitlestring | null
descriptionstring | null
month_keystring | null
The month of the action (YYYY-MM): the planner's column.
scheduled_datenumber | null
The 1st of the month at 12:00 UTC (ms), to sort; the month is month_key.
sub_actionsarray<object>
The checklist, in order.
content_briefobject | null
Content brief (target keyword, outline…), when it has one.
backlink_detailsobject | null
Backlink details (domain, DA, cost, contact status), when it has them.
ordernumber
Position inside its month column, when it was moved by hand.
pack_idstring | null
The pack it was created from (seo_planner.packs.get).
pack_sourcestring | null
Where that pack was: org, parent or system.
pack_item_idstring | null
template_idstring | null
The action template it was created from.
template_sourcestring | null
system (the MB Suite library) or org.
source_keystring | null
The source_key it was created with (seo_planner.items.create), if any.
Adds an action to the SEO Planner in a month: title, type is one of blog_post, on_page_seo, speed_performance, technical_seo, website_audit, ai_geo, backlink, keyword_research, seo_analytics, international_seo, local_seo, setup_tools, competitor_analysis, link_audit, rank_tracking, client_report, custom; month_key (YYYY-MM) is the month column where it appears. Optional: status (default pending), subtitle, description, sub_actions (an ordered checklist of titles, each optionally completed), content_brief (target keyword, outline, keywords to include…) and backlink_details (domain, DA, cost, contact status). The creator is the caller. To create it from a saved template use seo_planner.action_templates.apply; from a pack, seo_planner.packs.apply. Returns the action with created: true. Optional source_key (letters, digits and : . _ -, 1 to 200 characters, starting with a letter or digit; 400 invalid_input otherwise): a key of yours that identifies the action, unique in the organization and kept on it (returned by seo_planner.items.list and get, and seo_planner.items.list?source_key= finds it). If an action with that source_key already exists here, nothing is created, no event fires and that action is returned as it is now (its month or content may differ from what you sent) with created: false, so running a script again never duplicates it (only this operation keeps the key unique: restoring from the trash an action whose key was used again, or a write from the app, can leave two, and then the one with the lowest id is returned); without source_key every call creates a new action. The key cannot be changed afterwards. Cost: one write, plus one read to look for the key when source_key is sent. Requires full access to the SEO Planner.
Escopo
seo_planner:write
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_createNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.create".
The content brief of a blog_post or on_page_seo action.
backlink_detailsobjectcorpoopcional
The backlink details of a backlink action.
source_keystringcorpoopcional
A key of yours that identifies this action (letters, digits and : . _ -, up to 200 characters), unique in the organization. If an action with this source_key already exists, nothing is created and that action is returned with created: false. It cannot be changed later.
Changes one or more fields of an action: title, subtitle, description, type, status (pending, in_progress, completed), sub_actions (the whole ordered checklist: items with the id of an existing sub-action keep it, the rest are new, missing ones are removed), content_brief and backlink_details (null removes them) and order (position in its column). To move it to another month use seo_planner.items.move. Unknown fields are rejected. Setting status to completed also fires seo_planner.item.completed. Sending the same values changes nothing (changed: false). Requires full access to the SEO Planner.
Escopo
seo_planner:write
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_updateNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.update".
Moves an action to the month month_key (YYYY-MM), like the move-to-next/previous-month buttons of the planner, keeping its status, sub-actions and comments. Moving it to the month it is already in changes nothing (changed: false). Requires full access to the SEO Planner.
Escopo
seo_planner:write
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_moveNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.move".
Marks an action as completed; with complete_sub_actions: true it also ticks every sub-action of its checklist. Idempotent: an action that is already completed (with its sub-actions ticked, if asked) changes nothing (changed: false). Fires seo_planner.item.completed when the status changes. Requires full access to the SEO Planner.
Escopo
seo_planner:write
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_completeNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.complete".
curl-X POST "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/complete" \
-H"Authorization: Bearer $MB_API_KEY"
Testar com a sua API key de teste
Com uma API key de teste o pedido vai sempre para a sua organização de prática: dados de exemplo que você pode reiniciar.
curl-X POST "https://api.mb-suite.com/v1/seo-planner/items/{item_id}/complete" \
-H"Authorization: Bearer $MB_TEST_KEY"
DELETE/v1/seo-planner/items/{item_id}
Delete an SEO planner action
seo_planner.items.delete
IrreversívelDesde 2026-11-01
Deletes an action of the SEO Planner. It goes to the 30-day trash, where an owner or admin can restore it (platform.trash.restore); its comments stay attached and come back with it. 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.
Com uma API key, este DELETE roda direto: o registro fica 30 dias na lixeira e a resposta traz o seu trash_item_id. Com um token OAuth, e pelo MCP, pede dry_run → confirm_token.
Escopo
seo_planner:writee «Permitir exclusões» (seo_planner:delete no OAuth)
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_deleteNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.delete".
Deletes up to 200 actions of the SEO Planner, like the selection bar of the table view; each one goes to the 30-day trash and can be restored on its own. Ids that do not exist in this organization are skipped and returned in not_found. Outside the app it requires a dry run (which lists what will be deleted) and a confirm_token. Requires full access to the SEO Planner.
Pede confirmação: primeiro dry_run: true (prévia e confirm_token, válido por 10 minutos e por uma única execução), depois o mesmo corpo com confirm_token. Em algumas poucas, só com certos dados: a descrição diz quando. Por que e como: Prévia e confirmação.
Escopo
seo_planner:writee «Permitir exclusões» (seo_planner:delete no OAuth)
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_bulk_deleteNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.bulk.delete".
Change the status or month of many SEO planner actions
seo_planner.items.bulk.update
EscritaEm massa · até 200Desde 2026-11-01
Applies the same change to up to 200 actions, like the selection bar of the planner: status (pending, in_progress, completed) and/or month_key (YYYY-MM, moves them all to that month). Actions that already have those values are counted in unchanged; ids that do not exist are skipped and returned in not_found. Outside the app it requires a dry run and a confirm_token. Requires full access to the SEO Planner.
Pede confirmação: primeiro dry_run: true (prévia e confirm_token, válido por 10 minutos e por uma única execução), depois o mesmo corpo com confirm_token. Em algumas poucas, só com certos dados: a descrição diz quando. Por que e como: Prévia e confirmação.
Escopo
seo_planner:write
Permissão
Editar no módulo
Tool do MCP
seo_planner_items_bulk_updateNa superfície completa; na compacta, mb_execute_operation com id: "seo_planner.items.bulk.update".
