Pineprompt

List Source Url Prompt Analytics Tool

list-source-url-prompt-analytics-tool

Read-onlyIdempotent

Per-prompt citation analytics scoped to one source URL: how many distinct analyzed responses on each prompt cited the URL in the window, plus the most recent citation date. Paginated.

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": {
      "project_id": "<project_id>",
      "source_url_id": "<source_url_id>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "list-source-url-prompt-analytics-tool"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-indexed page number. Defaults to 1.
`tags`	No	Tag IDs (prompt classifiers) to limit responses by. Optional.
`sort_by`	No	Sort key. One of: citation_count, last_cited_on, prompt, monitor_name. Defaults to citation_count.
`end_date`	Yes	Inclusive UTC end of the analytics window. Must be on or after `start_date` and on or before today.
`interval`	No	Bucket granularity for time-series tools. One of: day, week, month, year. Required for time-series tools, ignored for aggregate tools.
`monitors`	No	Monitor IDs in the active project. Optional.
`per_page`	No	Page size, 1-100. Defaults to 25.
`sort_dir`	No	asc or desc. Defaults to desc.
`countries`	No	ISO-3166-1 alpha-2 country codes to include. Optional.
`platforms`	No	AI platforms to include. Optional. Values: chatgpt, perplexity, gemini, grok, copilot, claude, google_ai_mode, google_ai_overview.
`project_id`	Yes	Project to compute analytics for.
`start_date`	Yes	Inclusive UTC start of the analytics window. ISO 8601 date (YYYY-MM-DD).
`source_url_id`	Yes	Source URL to scope the analytics to. Must belong to a source in the named project.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by defining the aggregation semantics ('distinct analyzed responses' that 'cited the URL') and the pagination trait, though it says nothing about permission requirements or how interval is ignored for this aggregate tool.

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?

A single front-loaded sentence whose colon clause defines the two returned measures, closing with a one-word pagination note. No filler, no restatement of the title beyond what is needed to convey scope.

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 13-parameter aggregate tool with no output schema, the description does what matters: it names the measures returned and flags pagination. What is missing is minor, mainly confirmation that filters like platforms/countries/monitors narrow the counted responses and that interval is irrelevant here.

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%, including the enum-like value lists and date constraints, so the baseline is 3. The description only reinforces source_url_id scoping and the date window; it adds no syntax or default information beyond what the schema already documents.

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 a specific verb+resource (per-prompt citation analytics) and pins the scope ('scoped to one source URL'), then defines the exact metrics returned: distinct analyzed responses per prompt plus most recent citation date. That scoping distinguishes it from the broader list-prompt-analytics-tool sibling without needing to name it.

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?

Usage is only implied by the scope phrase 'scoped to one source URL' and 'in the window'; there is no explicit when-to-use/when-not guidance and no named alternative for the same question at a different scope (e.g. all sources vs one source URL vs time series). An agent must infer the routing from sibling names.

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

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