Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

postreportadhawk

Retrieve Adhawk analytics reports including impressions, demographics, dwell time, events, and network metrics by specifying dataset type and date range.

Instructions

Returns Adhawk dataset based on the provided post parameters.

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

Input Schema

NameRequiredDescriptionDefault
requestBodyNoRepresents the body of a request for an AdHawk dataset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states it 'returns' a dataset, but fails to mention side effects, data mutability, or expected response format. The verb 'postreportadhawk' suggests a POST operation, yet the description does not clarify if it creates a report or retrieves data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it sacrifices completeness for brevity. It does not earn its place by providing actionable information beyond restating the tool's name.

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

Completeness2/5

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

Given the complexity of the nested requestBody with many optional fields and no output schema, the description is insufficient. It lacks explanation of what each dataset type returns, how to interpret the response, or examples. An agent cannot reliably use this tool based on the description alone.

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 the baseline is 3. The description adds no additional meaning beyond what is already in the schema's property descriptions. It does not help an agent understand which parameters are critical or how to combine them.

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 clearly states it returns an Adhawk dataset based on post parameters. However, it does not differentiate from sibling tools like getreportbyid or postreportexport, missing the opportunity to clarify when to use this specific endpoint.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing a prior report or authentication, nor any indication of which parameter combinations are valid.

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

Deploy Server

Other Tools