Skip to main content
Glama

ADS Beast

seo_ai_citation_optimize

Read-only

Rewrites guidance for a page or text so AI answers can quote it: definition blocks, quotable statements, FAQ. AI: 1 AI request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_ai_citation_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNohttps:// page URL.
contentNoThe text, when there is no URL.
keywordNoTarget search query.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the cost ("1 AI request") and the structural form of the rewrite (definition blocks, quotable statements, FAQ). However, it does not clarify whether "rewrites" means it modifies the live page or merely returns suggested text, which is the key ambiguity an agent faces for a rewrite tool.

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

Conciseness5/5

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

Two compact sentences, front-loaded with the core action and goal before the output detail. The terse "AI: 1 AI request" line delivers cost information with no wasted words.

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 single-call rewrite tool with no output schema and open-world access, the description covers intent, cost and output structure reasonably well. It leaves open whether the page is actually modified, what happens to the keyword and client_id inputs, and how the result is returned, which an agent needs in order to call it confidently.

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 75%, with url, content and keyword already documented in the schema, so the schema carries most of the burden. The description's phrase "for a page or text" usefully signals the url-vs-content alternative, but it says nothing about keyword or the undocumented client_id parameter. Baseline 3 is appropriate given the high coverage.

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 pairs a specific verb ("Rewrites") with a concrete resource ("guidance for a page or text") and states the outcome goal ("so AI answers can quote it"). It also enumerates the deliverables (definition blocks, quotable statements, FAQ), which makes the tool's output shape clear. It does not explicitly distinguish itself from near siblings such as aeo_content_optimize, so it stops short of a 5.

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?

Usage is only implied: the agent can infer it applies when you want content to be citable by AI answers, and that it accepts either a URL or raw text. There is no explicit when-to-use versus when-not-to-use guidance, no mention of prerequisites, and no routing to an alternative tool for adjacent goals.

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.