Skip to main content
Glama

Outil.io

Update poster

update_poster
Destructive

Remplacer le contenu d’une affiche (document complet, version exacte). Renvoie le nouvel aperçu.

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": {
      "posterId": "<posterId>",
      "version": "<version>",
      "poster": "<poster>"
    },
    "name": "update_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
posterYes
versionYes
posterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known; the description usefully confirms the operation replaces the entire document content and returns a new preview. It does not explain version-conflict behavior, whether omitted fields are cleared, or permission requirements — meaningful gaps for a destructive, nested-payload mutation.

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?

Two short, front-loaded sentences with no filler; the scope constraint precedes the return-value note. It is efficient, though its brevity leaves substantive gaps rather than being genuinely complete.

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

Completeness2/5

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

This is a destructive mutation with three required parameters, a deeply nested payload with multiple enums and unions, no output schema, and open-world side effects. Given that complexity, the description should explain version semantics, replace-vs-merge behavior, and failure modes, but it supplies only one scoping clause and one sentence about the returned preview.

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

Parameters4/5

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

Top-level schema coverage is 0% and the three required parameters, including a large nested 'poster' object, carry no descriptions at the top level. The description compensates partially by signaling that 'poster' must be the complete document and 'version' an exact version (optimistic concurrency), which adds real meaning beyond the schema, though it does not describe posterId or the consequence of a version mismatch.

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 and resource ('Remplacer le contenu d'une affiche') and clarifies the scope as a whole-document replacement with an exact version, which implicitly separates it from partial-update tools like update_page. It does not, however, name or distinguish any actual sibling such as create_poster.

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

Usage Guidelines3/5

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

The parenthetical 'document complet, version exacte' implies the tool is for full replacements against a known version rather than incremental edits, which is usable guidance. There is no explicit when-to-use/when-not, no mention of what to call instead for partial edits, and no stated prerequisites.

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.