DevTune MCP

devtune_get_citation_analysis

Read-onlyIdempotent

Backward-compatible alias for top citation pages in AI search results, with the same topicId, promptId and platform filters. Prefer devtune_get_top_citation_pages for new workflows. Returns the same coverage state: an unavailable window has not been rolled up yet, so an empty list is not a measured zero.

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

Input Schema

Name	Required	Description
`cursor`	No	Opaque cursor from the previous response. Continue with the same window, search and filters; a cursor used with any of them changed, or a filtered list's cursor after the list was republished, is refused, so start again without one. Filtered lists page through their first 100,000 rows. Unfiltered lists retain their existing pagination.
`search`	No	Optional prefix search within citation URLs and domains.
`topicId`	No	Only citations recorded under this topic, by the id devtune_list_topics returns. A prompt moved to another topic keeps its earlier citations under the earlier topic.
`pageSize`	No	Results per page (1-100). Defaults to 25.
`platform`	No	Only citations from this AI platform: chatgpt-search, perplexity, google-ai, google-ai-mode or bing-copilot-search, plus claude and xai-search where the account tracks them.
`promptId`	No	Only citations from this tracked prompt, by the id devtune_list_prompts returns.
`windowDays`	No	Rolling window in days: 30 or 90. Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor from the previous response."New value: +"Opaque cursor from the previous response. Continue with the same window, search and filters; a cursor used with any of them changed, or a filtered list's cursor after the list was republished, is refused, so start again without one. Filtered lists page through their first 100,000 rows. Unfiltered lists retain their existing pagination."

addedInput schema / properties / platform

Added value: +{
+  "description": "Only citations from this AI platform: chatgpt-search, perplexity, google-ai, google-ai-mode or bing-copilot-search, plus claude and xai-search where the account tracks them.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / promptId

Added value: +{
+  "description": "Only citations from this tracked prompt, by the id devtune_list_prompts returns.",
+  "format": "uuid",
+  "type": "string"
+}

addedInput schema / properties / topicId

Added value: +{
+  "description": "Only citations recorded under this topic, by the id devtune_list_topics returns. A prompt moved to another topic keeps its earlier citations under the earlier topic.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real operational context the annotations do not — that an unavailable window has not been rolled up and an empty list is not a measured zero. It does not describe ordering or result shape, keeping it short of a 5.

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?

Three sentences, front-loaded with identity and the preferred alternative, then the one non-obvious result caveat. No waste.

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?

For a read-only alias with no output schema and fully documented parameters, the description covers identity, migration guidance and the empty-result caveat. Only minor gaps remain (result ordering/aggregation shape), which the schema cannot supply but which are not essential for correct invocation.

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 description coverage is 100% and each parameter has rich inline documentation (cursor semantics, platform enum list, windowDays values), so the schema does the heavy lifting. The description only restates that topicId, promptId and platform filters exist, adding no new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (top citation pages in AI search results) with its filter scope, and names the sibling it aliases and the sibling an agent should prefer. An agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says "Prefer devtune_get_top_citation_pages for new workflows," giving both the alternative and the condition that selects it, while framing this tool as backward compatibility only.

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

All DevTune MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?