Skip to main content
Glama

sales_post

Read-onlyIdempotent

What one post sold in the owner's store since it was made, the post's Sales panel in Hookbird. Free. The same post on several networks counts as one: each network has its clicks, orders and revenue and its tracked links (in the post, or "bio" for a bio or story link), then the post's discount codes with their orders, and its latest orders (matchedBy: "code", "link", "first_link" or "pixel"). Pass the "id" of a post (list your posts, or a postId from sales_overview). Use it when the user asks how a given post or video sells, or for its links and codes. The numbers come only from the store the owner connected; "connected" false means no store is connected yet (they connect one on the Sales page). Never make up or promise sales.

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": {
      "postId": "<postId>"
    },
    "name": "sales_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe "id" of the post

Output Schema

NameRequiredDescriptionDefault
codesNo
errorNo
titleNo
postIdNo
totalsNo
bioLinkNo
currencyNo
networksNo
connectedNo
salesPageNo
latestOrdersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses real behavior: multi-network posts collapse into one result with per-network clicks, orders, revenue and tracked links, plus discount codes and latest orders with matchedBy values ('code', 'link', 'first_link', 'pixel'). It also flags the data-source constraint (only the owner's connected store), explains that 'connected: false' means no store yet, and warns never to fabricate or promise sales.

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 is front-loaded, but the first sentence is a convoluted nominal phrase and later sentences embed nested parentheticals and inline enumerations, with stray indentation from the source formatting. Nearly every sentence carries useful content, yet the packing makes it slower to parse than necessary.

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

Completeness5/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-shape documentation is not required, yet the description still characterizes the payload (per-network links, codes, latest orders, matchedBy provenance). Combined with the connected-store caveat and the no-fabrication warning, an agent has everything needed to call and report this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is a 3, but the description adds sourcing meaning the schema lacks: the postId should come from the owner's post list or from a sales_overview postId. It does not restate the maxLength or format, which the schema already handles.

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 opening sentence states a specific resource and scope: what a single post sold in the owner's connected store since creation, framed as the post's Sales panel. It distinguishes itself from siblings by naming sales_overview as the source of a postId and pointing to a post-listing route, so an agent can separate it from sales_bio_link, sales_code, and sales_overview.

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?

It gives explicit usage context: 'Use it when the user asks how a given post or video sells, or for its links and codes,' plus prerequisite guidance on where the postId comes from (post list or sales_overview). It stops short of stating when to prefer a sibling such as sales_overview instead, so it is clear context without full alternative routing.

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