AthenaHQ

get_content_citation_prompts

Read-only

For a single tracked content item, list every prompt whose AI responses cited it — with citations, citation %, and estimated impressions. Use after get_tracked_content to drill into which prompts a given URL is appearing for. This is CITED-BY, measured over the requested date range, not the targeting the page was written for: an empty prompts array means no AI response cited this URL in that window, which is expected for new or never-cited pages and is not missing data. For the prompts a page was written to target, read prompts on get_content_detail (or prompt_ids on list_content) — those come from the content record itself and do not depend on any citation having happened.

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": {
      "website_id": "<website_id>",
      "content_id": "<content_id>",
      "filters": "<filters>"
    },
    "name": "get_content_citation_prompts"
  }
}

Input Schema

Name	Required	Description	Default
`filters`	Yes
`mentioned`	No
`content_id`	Yes
`website_id`	Yes

Output Schema

Name	Required	Description	Default
`prompts`	Yes
`content_id`	Yes
`content_url`	Yes
`content_normalized_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- removedOutput schema / properties / content_normalized_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / content_normalized_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / content_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / content_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / prompts / items / properties / estimated_impressions / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / prompts / items / properties / estimated_impressions / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare this a non-destructive read operation, and the description adds substantive behavioral context: results are measured over the requested date range, only prompts whose AI responses cited the URL are returned, and an empty array is expected for new or never-cited pages. This goes well beyond what the annotations provide.

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?

The description is front-loaded with purpose, then usage, then the empty-result interpretation, then the alternative targeting source. Every sentence carries information an agent would otherwise have to infer.

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 tool with an output schema and annotations, the description covers the important semantic risks: citation-based vs targeting prompts and empty-array interpretation. The only gap is the lack of parameter-level guidance for the complex filters object, but the nested schema supplies most of that detail.

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?

The top-level parameters (website_id, content_id, filters) are not explained in the description, and the context reports very low schema description coverage for the top level. The nested filter schema is detailed, but the description does not compensate for undocumented required parameters or the unexplained `mentioned` boolean.

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?

The description states a precise verb and resource: list every prompt whose AI responses cited a single tracked content item. It explicitly defines this as the CITED-BY view and distinguishes it from the page's targeting prompts, so the agent can tell it apart from get_content_detail and list_content without opening their schemas.

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?

It names the prerequisite flow ('Use after get_tracked_content') and the specific alternative for targeting prompts. It also explains the meaning of an empty result, so the agent knows not to treat it as an error or missing data.

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

All AthenaHQ 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?