Skip to main content
Glama

ADS Beast

get_social_queue

Read-only

Return the next business profiles to message by hand, best first, within today's remaining cap per platform: profile link, signals (books by DM, by phone, competitor tool), the drafted first message in the profile's language (no link) and the follow-up with a tracked link to send after a reply. Nothing is sent by this tool.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_social_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many profiles. Clamped into 1..100.
platformNoOnly this platform.
campaign_idYesSocial campaign id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description reinforces the safety story with 'Nothing is sent by this tool'. Beyond that it discloses useful behavior the annotations cannot: results are ordered best-first, are bounded by a per-platform daily cap, and each item carries language-matched drafts with the link only in the follow-up. It does not say whether fetching advances or consumes the cap (idempotency), which is the one material gap.

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?

A single front-loaded sentence with the action and ordering first, followed by the item contents and the safety disclaimer — no filler. It is dense, however, packing four return-field descriptions into one clause chain, which reads more like a spec dump than a crisp definition.

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?

No output schema exists, so the description carries the return-value burden and does so fully: profile link, signals, drafted first message in the profile's language without a link, and a follow-up with a tracked link. Combined with cap and ordering semantics, an agent has everything needed to call it and interpret the result.

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 'limit' clamping and the platform enum are already documented. The description still adds meaning by tying 'limit' to today's remaining per-platform cap and by making clear that 'platform' narrows an otherwise cross-platform, ranked queue. That is modest but real added context above the baseline of 3.

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 — 'Return the next business profiles to message by hand, best first' — plus the scoping constraint of today's remaining cap per platform. The explicit 'Nothing is sent by this tool' separates it from any send/post tool, so an agent can identify it without opening the 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?

'To message by hand' and 'best first' make it clear this is a manual outreach work-queue rather than an analytics or listing tool, and 'within today's remaining cap per platform' tells the caller when the result set is complete. It stops short of naming an alternative (e.g. competitor_social_signals) or stating when not to call it, so it is not a full 5.

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.