Skip to main content
Glama

ADS Beast

aeo_content_optimize

Reformats a client's page for citation by AI models (Q&A version, FAQ blocks, JSON-LD) and saves the recommendations. AI: 1 AI request.

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": {
      "page_url": "<page_url>",
      "client_id": "<client_id>"
    },
    "name": "aeo_content_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_urlYesThe page to optimise.
client_idYes
focus_queryNoThe AI query to win.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds two genuinely useful facts beyond them: that recommendations are persisted ('saves the recommendations') and a cost signal ('AI: 1 AI request'). However, it is ambiguous whether the page itself is modified or only recommendations are stored, and with no output schema the return shape is undisclosed.

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 tight sentences with the outcome front-loaded and the cost note appended as a compact tag. Nothing is padded, though the artifact list is slightly dense and could be structured more clearly.

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 tool with side effects (saving recommendations), an undisclosed output shape, and one undocumented parameter, the description says enough to pick the tool but not enough to predict what it returns or where results land. Missing: whether the page is rewritten, and where recommendations are stored.

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 67%, above the point where the schema does most of the work. The description ties vaguely to 'page' but adds no meaning for focus_query or the undocumented client_id, so it does not compensate for the coverage gap. Baseline 3 is appropriate.

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 ('Reformats'), the resource ('a client's page'), and the concrete artifacts produced (Q&A version, FAQ blocks, JSON-LD), plus that recommendations are saved. It does not distinguish itself from the near-identically named sibling seo_ai_citation_optimize, leaving the agent to guess which to pick.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of how this differs from seo_ai_citation_optimize. Usage is only implied by the purpose statement, which is a real gap given a sibling with an almost identical name.

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.