Reel-E

Listing analytics

get_listing_analytics

Read-onlyIdempotent

The listing website's analytics over a period: visits, visitors, video plays, how much of the video people watch, inquiries (leads) and top traffic sources. The full chart is in the listing's analytics in Reel-E. Owner visits are not counted.

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": {
      "listingId": "<listingId>"
    },
    "name": "get_listing_analytics"
  }
}

Input Schema

Name	Required	Description
`days`	No	Period in days. Default 30.
`surface`	No	Optional: only the website, or only the video links.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: owner visits are excluded from the counts, and the complete chart is available in Reel-E's own analytics view, which helps an agent interpret and route the results.

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 resource and the metric list, with no filler. The phrase 'how much of the video people watch' is slightly informal where 'video watch-through' would be tighter, but it is still clear.

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?

An output schema exists, so return values need not be explained, and the description nonetheless lists the metric categories the agent will receive. Combined with complete schema coverage and full read-only annotations, the only real omission is the absence of guidance about when this is the right tool versus other listing tools.

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%, with enums documented for both 'days' and 'surface', so the schema carries parameter meaning. The description only implies a time period ('over a period') and says nothing about the surface filtering options or how listingId should be obtained, adding no real semantics beyond the schema.

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 the exact resource (a listing website's analytics) and enumerates the metrics returned: visits, visitors, video plays, watch-through, inquiries/leads, and top traffic sources. It is clearly distinguishable from all editing-oriented siblings, though it never explicitly contrasts itself with any other analytics or status 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?

Usage is only implied: the description says the full chart lives in Reel-E's analytics UI, suggesting this tool is for pulling the numbers programmatically. There is no explicit when-to-use versus when-not, no mention of alternatives such as get_listing_status, and no guidance on which period to choose.

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

All Reel-E 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?