Skip to main content
Glama

Outil.io

Insert synced component

insert_synced_component
Destructive

Insère une section synchronisée existante (list_synced_components) dans des pages qui ne l’ont pas : en haut (en-tête), en bas (pied de page) ou après une section. Une page qui l’a déjà est ignorée.

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": {
      "componentId": "<componentId>",
      "pageIds": "<pageIds>"
    },
    "name": "insert_synced_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdsYes
positionNotop
componentIdYes
afterSectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/destructive profile is covered. The description adds one real behavioral trait beyond that — existing occurrences are skipped rather than duplicated — but says nothing about why the operation is destructive, whether it can overwrite adjacent content, or what permissions are needed.

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?

A single front-loaded sentence that states the action, the placement options, and the skip rule with no filler. The parenthetical reference to list_synced_components is dense but earned.

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 a 4-parameter mutation tool with no output schema and no schema descriptions, the definition covers placement modes and idempotency but leaves the relationship between position and afterSectionId implicit (are they exclusive?) and never describes the effect on the target pages. Just enough to act, not enough to act confidently at scale.

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 description coverage is 0%, so the description carries the burden: it does clarify that position supports top/header, bottom/footer, and that 'after a section' is a third placement mode via afterSectionId. It says nothing about componentId format or the pageIds batch limit (max 200) that the schema enforces.

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?

The description names a specific verb and resource ('Insère une section synchronisée existante') and ties it to the sibling lookup tool (list_synced_components), which makes the intent unambiguous. It stops short of explicitly differentiating itself from insert_html_section, so 4 rather than 5.

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?

It states the context of use (pages that do not already have the component) and the exclusion (pages that already have it are ignored), and points to list_synced_components for discovery. It gives no guidance on when to prefer insert_html_section or another insertion tool instead.

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.