Skip to main content
Glama

sales_overview

Read-onlyIdempotent

What the brand's posts sold in its own store over the last 7, 30 or 90 days: the numbers of Hookbird's Sales page. Free. It has the revenue and orders that came from posts and their share of all the store's sales, the clicks on tracked links and the rate that became orders, the posts that sold best (hook, hook pattern, format, presenter, networks; the same post on several networks counts once), sales per network, format, hook pattern and presenter, how orders were matched to posts (matchedBy: "code" a discount code made for a video, "link" the last tracked link visited before the order, "first_link" an earlier one, "pixel" the website pixel), the latest orders and the connected stores with their status. Use it when the user asks what sold, which posts or videos make money, or which hooks, formats, presenters or networks bring orders, and before suggesting content that should sell. sales_post has one post in detail. The numbers come only from the store the owner connected (Shopify, WooCommerce, Stripe or a website with the Hookbird pixel), in "currency" (other currencies are listed apart). "connected" false means no store is connected yet: say so and that they connect one on the Sales page (salesPage); a store type can show there as not available yet. A store with status "error" says why in lastError. No sales is a real answer: never make up, estimate or promise sales.

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

Input Schema

NameRequiredDescriptionDefault
daysNoThe period in days (default 30)

Output Schema

NameRequiredDescriptionDefault
daysNo
errorNo
storesNo
totalsNo
formatsNo
currencyNo
networksNo
topPostsNo
connectedNo
matchedByNo
salesPageNo
presentersNo
hookPatternsNo
latestOrdersNo
websitePixelNo
otherCurrenciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the data source constraint (only the owner-connected store: Shopify, WooCommerce, Stripe or pixel), how unmatched currencies are reported, what connected=false and status="error"/lastError mean, and an anti-fabrication rule ("No sales is a real answer: never make up, estimate or promise sales"). That is exactly the operational context an agent needs to answer honestly.

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 purpose statement is front-loaded and the guidance sentences earn their place, but the middle paragraph is a long enumerated inventory of return fields that duplicates the existing output schema and is delivered in dense compound sentences. Trimming that inventory would make the definition sharper without losing callable information.

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 a single-parameter read tool with full annotations and an output schema, everything an agent needs is present: triggers, alternatives, data provenance, empty-state handling, and honesty constraints. The only shortfall is redundancy, since return-value structure is re-explained despite the output schema already covering it.

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 coverage is 100% with a single enum parameter and documented default, so the schema already carries the semantics. The description only mirrors the 7/30/90 options without adding format, behavior-at-boundary, or defaulting detail beyond what the schema states; baseline 3 applies.

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?

Opens with a concrete verb and resource: what the brand's posts sold in its own store over 7/30/90 days, and explicitly anchors it to Hookbird's Sales page. It also distinguishes itself from sales_post ("sales_post has one post in detail"), so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ("when the user asks what sold, which posts or videos make money, or which hooks, formats, presenters or networks bring orders") plus a proactive case ("before suggesting content that should sell"). It also names the alternative tool for the single-post case and routes the no-store scenario to the Sales page.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources