Skip to main content
Glama

SEO Rank Fixer

Content briefs

content_briefs
Read-onlyIdempotent

Briefs for one site's best openings: searches it ranks 4-20 for on Google, or questions its pages do not answer, each joined with what AI assistants (ChatGPT, Claude, Gemini, Perplexity) say when asked the same thing, and the steps to rank in the top 3 and get quoted by AI. Steps the page already has are marked done. Free; 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": "content_briefs"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the data sources being joined (Google rankings plus ChatGPT/Claude/Gemini/Perplexity answers), that completed steps are flagged as done, and that the call consumes no credits.

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?

A single dense sentence front-loads the core resource and then enumerates the joined data and the 'done' marking, followed by a short cost note. It is efficiently packed with no filler, though the long sentence does stack several clauses.

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 has to convey the return shape, and it does: openings, AI answers, ranked steps with completion status. What remains unstated is volume, pagination, or ordering of the returned briefs — minor, but a real gap for a report-style tool.

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?

There is one parameter with 100% schema description coverage pointing at list_sites, so the schema carries the meaning. The description does not mention siteId or its scoping behavior at all, leaving this at the baseline for well-documented single-parameter tools.

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 is unusually specific about the resource: briefs for one site covering queries ranking 4-20, unanswered questions, joined AI-assistant answers, and remediation steps. It reads as a noun phrase rather than an explicit verb, and it does not name a sibling to contrast with (e.g. opportunities or ai_answers), 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent how this differs from opportunities, ai_answers, or competitor_gap, nor what prerequisite state a site must be in. The only usage-adjacent signal is 'Free; asks nothing,' which speaks to cost rather than selection.

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.