SEO Performance MCP

Cohort report across posts

cohort_report

Read-only

Ranks posts in a filtered cohort by refresh verdict and confidence, then shows which pages to update next.

Instructions

Run the verdict engine across a cohort (filtered by tag and/or min-age) and return a ranked table sorted by verdict priority then confidence.

Practical use: 'which three posts should I refresh this week?' - the top three rows with verdict=refresh and highest confidence are the answer.

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": "cohort_report"
  }
}

Input Schema

Name	Required	Description
`urls`	No	Explicit list of post URLs to include. Overrides sitemap discovery.
`limit`	No
`window`	No
`sitemap_url`	No	Sitemap URL to enumerate the cohort. Falls back to POSTS_SITEMAP_URL env var.
`min_age_days`	No

Output Schema

Name	Required	Description	Default
`rows`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.2Oct 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context about result ordering (verdict priority, then confidence) and the sitemap env-var fallback, but says nothing about cost/latency of scanning a cohort or how many rows are returned relative to the limit.

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 sentences, front-loaded with the core operation and followed by a concrete example; no filler. The example sentence earns its place by making the ranked output interpretable.

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?

An output schema exists, so return values need not be re-explained, and the description covers selection and ordering. But with 40% param coverage and a phantom 'tag' filter, an agent still lacks details on how cohort membership is actually determined (urls vs. sitemap vs. defaults).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40% across five parameters, so the description should compensate. It mentions min-age and a 'tag' filter — but tag is not a parameter at all, and it says nothing about urls, limit, or window semantics. The single nod it gives is partly misleading rather than clarifying.

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?

It states a concrete verb+resource: run the verdict engine across a cohort, returning a ranked table sorted by verdict priority then confidence. That distinguishes it from the per-post siblings like posts_verdict. However, it claims filtering 'by tag and/or min-age' when no tag parameter exists in the schema, which muddies what the tool actually does.

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?

The practical-use sentence ('which three posts should I refresh this week?') gives a clear, actionable scenario for selecting this tool and even describes how to read the result. No explicit alternatives or exclusions are named (e.g., vs. posts_verdict), so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server