Skip to main content
Glama

SEO Rank Fixer

Missing questions

missing_questions
Read-onlyIdempotent

The questions one site is missing, in three channels: Google and Bing searches (ranking off page one or below the top 3, or won by a competitor), answer boxes (questions its pages do not answer, or where Google quotes another site) and AI assistants (saved customer questions ChatGPT, Claude, Gemini and Perplexity answer without naming or citing it). Each has why it is missing, searches a month where known, and the link to fix it. From stored data only; asks nothing.

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": {
      "siteId": "<siteId>"
    },
    "name": "missing_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: results come from stored data only, each item carries a 'why it is missing', a monthly search volume 'where known', and a fix link — telling the agent what it can and cannot rely on in the payload.

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?

The purpose is front-loaded in the opening clause, followed by the channel breakdown, the per-item fields, and the stored-data caveat. It is dense but every clause carries information; the long first sentence is the only mild structural cost.

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?

With no output schema, the description carries the burden of describing return values, and it does so (missing reason, monthly searches, fix link). Safety behavior is covered by annotations; only result volume/pagination is unspecified, which is minor for a single-site lookup.

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?

Only one parameter exists and schema coverage is 100%; the schema already says siteId is 'a site id from list_sites'. The description adds no constraint or format detail about the parameter, so the baseline 3 applies.

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 resource ('the questions one site is missing') and enumerates the three channels it covers (search rankings, answer boxes, AI assistants), so an agent knows exactly what comes back. It does not name a sibling to contrast with, which keeps it from 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?

There is no explicit when-to-use or when-not guidance relative to siblings like opportunities, competitor_gap, or content_briefs. The clause 'From stored data only; asks nothing' implicitly tells an agent this is a passive, non-scanning read rather than a live query, which is useful but only implied usage guidance.

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.