Skip to main content
Glama

modify_article_blocks

Выполнить последовательные операции CRUD над блоками статьи. Операции применяются по порядку. Все операции адресуют блоки по их идентификатору (blockId), а не по индексу — поэтому порядок блоков может меняться произвольно, а id остаются стабильными. Идентификаторы блоков можно получить через get_article_blocks или get_article. Семантика move симметрична insert: блок с blockId перемещается так, чтобы оказаться сразу после блока afterBlockId (или в начало, если afterBlockId=null). Чтобы поменять местами два блока A и B, лежащих в порядке [..., A, ..., B, ...], необходимо ДВЕ операции move: [{"action":"move","blockId":"<B.id>","afterBlockId":"<блок перед A>"}, {"action":"move","blockId":"<A.id>","afterBlockId":"<блок перед B>"}]. Не более 100 операций за вызов, не более 50 блоков в одной операции insert. Если добавляешь много объёмного текста, не складывай его весь в один вызов — разбивай на несколько последовательных вызовов меньшими порциями блоков, иначе ответ может оборваться по длине и вызов придёт с неполными аргументами.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "article_id": "<article_id>",
      "operations": "<operations>"
    },
    "name": "modify_article_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesИдентификатор статьи
operationsYesСписок операций над блоками статьи в виде одного из объектов: {"action":"insert","afterBlockId":<id|null>,"blocks":[...]} (afterBlockId=null — вставка в начало статьи; не более 50 блоков за одну вставку) {"action":"modify","blockId":<id>,"block":{...}} (поле id внутри block игнорируется и принудительно заменяется на blockId) {"action":"remove","blockIds":[<id>,...]} {"action":"move","blockId":<id>,"afterBlockId":<id|null>} (переместить блок сразу после afterBlockId; null — в начало статьи). Не более 100 операций за вызов.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden and does substantial work: ordering guarantees, index-vs-id stability, move/insert symmetry, hard limits (100 ops, 50 blocks per insert), and a real failure mode (length-truncated responses producing incomplete arguments). It does not disclose error semantics for invalid blockIds, permission requirements, or whether a multi-operation call is atomic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and ordering semantics, then moving to the operational details. Some content (limits, afterBlockId=null meaning) is duplicated in the schema, and the swap example is verbose, but everything present is actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an unannotated batch-mutation tool, the description covers ordering, addressing, and size limits well, and an output schema exists for return values. However, nothing says whether a failed operation rolls back prior ones or leaves partial state, which is the key unknown for a sequential multi-op write.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description does add value beyond the schema by explaining move semantics and the exact two-move swap sequence, and by clarifying that insertion/move targets are positional anchors rather than indices.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: sequential CRUD operations over article blocks, addressing them by blockId rather than index. That clearly separates it from whole-article siblings like replace_article_text or set_article_content, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operating guidance: operations apply in order, ids must first be obtained via get_article_blocks or get_article, and the two-move swap procedure is spelled out step by step. Also warns to split large payloads across calls. Lacks an explicit 'use this instead of X when...' statement against sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources