Skip to main content
Glama
Sign In
ads-mcp

ads-mcp

by qalvinahmad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Petal Ads revenue summary

petal_revenue_summary
Read-onlyIdempotent

Summarize daily Petal Ads earnings trend and total revenue for a specified date range. Get a quick overview of recent ad performance.

Instructions

Daily Petal Ads earnings trend plus totals for a date range (defaults to the last 7 days). Convenience wrapper around petal_report.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of past days to cover (default 7; ignored when start_date is set)
currencyNoReport currency: CNY, USD, or EUR (default USD)
end_dateNoEnd date in YYYY-MM-DD (defaults to yesterday)
start_dateNoStart date in YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds context about output (daily trend plus totals), providing additional behavioral insight beyond annotations.

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?

Two concise sentences, front-loaded with purpose, no superfluous words.

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?

Lacks output schema but describes output as 'daily trend plus totals', sufficient for a simple query tool with rich annotations.

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 defaults already documented. Description restates defaults but adds no new parameter-level information, meeting the baseline.

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?

The description clearly states it provides 'Daily Petal Ads earnings trend plus totals for a date range' and identifies itself as a convenience wrapper around petal_report, distinguishing it from siblings.

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

Usage Guidelines4/5

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

Mentions default date range and that it is a wrapper around petal_report, implicitly guiding users to use this for quick summaries and petal_report for more detailed reports.

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