Pineprompt

Get Source Url Type Analytics Tool

get-source-url-type-analytics-tool

Read-onlyIdempotent

Citation breakdown by URL-type classification (e.g. article, documentation, product_page). Unpaginated: one row per URL-type enum value. Cannot be scoped by segment.

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>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get-source-url-type-analytics-tool"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Tag IDs (prompt classifiers) to limit responses by. Optional.
`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.
`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).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new behavioral facts: the result is unpaginated and returns exactly one row per URL-type enum value, which tells the agent the response cardinality and that no paging loop is needed.

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 short sentences with the core identity front-loaded and the cardinality/scope constraints immediately after; nothing is padded. The opening clause is a fragment lacking a verb, which slightly weakens readability but costs no space.

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 an aggregate analytics tool with no output schema, the description covers what matters most: what the rows are keyed by, how many to expect, and that paging and segment filters do not apply. It does not mention what metric each row carries (citation counts) or whether the interval parameter is ignored here, leaving a small gap.

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%, so all eight parameters are already documented in the schema, and the description adds no per-parameter syntax or defaults. The only parameter-adjacent signal is the absence of segment scoping, which is a constraint rather than added meaning, so the baseline 3 applies.

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 names a specific resource and verb-like operation: a citation breakdown keyed by URL-type classification, with concrete enum examples (article, documentation, product_page). That distinguishes it from the source-type sibling, though it never explicitly contrasts itself with get-source-type-analytics-tool.

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?

It supplies one useful exclusion — 'Cannot be scoped by segment' — which steers an agent away from segment-scoped paths, but there is no positive statement of when to pick this over get-source-type-analytics-tool or the list-source-url-* siblings. Usage is implied rather than prescribed.

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?