Skip to main content
Glama

ADS Beast

prepare_content_refresh

Prepare a refresh plan for an outdated page: what to rewrite, update or remove. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "url": "<url>",
      "reason": "<reason>"
    },
    "name": "prepare_content_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// page URL.
reasonYesWhy, with numbers (shown to the approver).
contentNoThe text, when the URL is unreachable.
client_idNo
publish_dateNoWhen the page was published, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that nothing is mutated, that a preview_id is stored, and that it is valid for 15 minutes and single use — exactly the operational constraints an agent needs. With readOnlyHint=false and destructiveHint=false already declared, this extra detail is the right kind of contribution; it omits approval/permission and error-path behavior.

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 sentences, purpose first and the preview/execute mechanics second, with no filler. The second sentence is telegraphic ('to show, then execute_prepared_change'), which slightly hampers readability but wastes no space.

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

Completeness4/5

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

For a 5-parameter, non-destructive prepare step with annotations and no output schema, the description supplies purpose, mutation safety, and the handoff contract. Only the unexplained client_id and any precondition on url reachability are left uncovered.

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 80%, so the schema already documents url, reason, content and publish_date. The description adds no parameter-level meaning and does not explain client_id, the one undocumented field, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Prepare a refresh plan for an outdated page') and enumerates the output decision space (rewrite, update, remove). This clearly separates it from create/write siblings and pairs it with execute_prepared_change.

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?

Names the situation (an outdated page) and explicitly routes the agent to the follow-up tool execute_prepared_change after showing the preview_id. It stops short of stating when to prefer this over alternatives like seo_content_write or aeo_content_optimize, but the two-step flow is unambiguous.

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.