Skip to main content
Glama
Sign In

CueHQ

by social.cuehq
OverviewDiscussionsAdmin

List cues

list_cues
Read-onlyIdempotent

Cues are live threads where someone is asking for what the user sells. Lists a brand's cues, newest first. scope matches the app's tabs: all, priority (early posts from big accounts), mentions (posts that name the user's handles or brand) and competitors (posts about competitors the user named). status surfaced is the waiting deck, engaged the cues the user replied to, skipped the ones they passed on.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many cues, 1 to 50.
scopeNoWhich tab: all, priority, mentions or competitors.all
statusNosurfaced (waiting), engaged (replied) or skipped.surfaced
brand_idNoThe brand id from brands. Leave it out when the user has one brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered structurally. The description adds genuine context beyond that: results are newest-first and status defaults to the waiting deck. It says nothing about pagination despite limit capping at 50, and nothing about what happens when a brand has no cues.

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?

Three dense sentences with no filler, and the scope/status decoding is compact rather than listy. The actionable statement arrives second, behind the definitional sentence, so it is slightly back-loaded.

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?

With no output schema, the description should characterize what a cue record looks like, and it only defines the concept abstractly without naming any returned fields. Filter semantics and ordering are complete, so an agent can call it correctly but cannot anticipate the response shape.

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%, so the baseline is 3, but the description goes further than the terse schema text by giving real meaning to each scope and status value ("priority (early posts from big accounts)", "engaged the cues the user replied to"). It does not carry the brand_id omission rule, which lives only in the schema.

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?

States a specific verb and resource ("Lists a brand's cues"), adds ordering ("newest first"), and defines the domain term ("live threads where someone is asking for what the user sells"). Reading it, an agent can separate this from the singular sibling get_cue 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 Guidelines4/5

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

Explicitly explains when each scope tab applies (priority = early posts from big accounts, mentions = posts naming the user's handles or brand, competitors = posts about named competitors) and decodes the status values. It gives no guidance on when to pick this over siblings like brands, get_cue or weekly_report, so it stops short of full routing guidance.

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

All CueHQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources