Skip to main content
Glama
GSC Opportunity MCP

GSC Opportunity MCP

by caomicc

get_raptive_revenue

Fetch real Raptive revenue, pageviews, and blended RPM for a specified day window and optional site to analyze monetization performance.

Instructions

Real Raptive revenue for the window: total $, pageviews, and blended RPM.

Requires RAPTIVE_CLIENT_ID/SECRET in .env; raises a clear error otherwise.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
site_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuine behavioral context by disclosing that RAPTIVE_CLIENT_ID/SECRET must exist in .env and that a clear error is raised otherwise, which is the kind of pre-flight info an agent needs. It says nothing about read-only semantics beyond the 'get' verb, rate limits, caching, or what the error looks like, leaving real gaps for an unannotated tool.

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, front-loaded with the resource and return contents, with the auth prerequisite second. Nothing is padded, though 'for the window' is vague enough that it costs a little clarity for its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description is right not to dwell on return shape, and the auth prerequisite is a valuable addition. However, for a two-parameter tool with zero schema documentation, leaving site_id entirely unexplained and offering no routing versus the page-performance sibling leaves the definition short of complete.

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?

Schema description coverage is 0% for both parameters. The description only obliquely gestures at 'days' via 'for the window' and never mentions 'site_id' at all, so the agent cannot tell from the definition whether site_id is required for a meaningful result or what omitting it does. With no schema documentation, the description needed to compensate and does not.

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?

States a specific resource and scope: real Raptive revenue over a window, returning total dollars, pageviews, and blended RPM. That is a clear verb+resource and enumerates the returned metrics, though it never distinguishes itself from the sibling get_raptive_page_performance, which an agent could easily confuse it with.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of alternatives such as get_raptive_page_performance for per-page breakdowns. Usage is only implied by the tool name and the phrase 'for the window'; the agent must infer that this is the aggregate-revenue call rather than the per-page one.

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