Skip to main content
Glama

ADS Beast

list_social_campaigns

Read-only

Return the Instagram/TikTok/Facebook prospecting campaigns: offer, platforms, cities with message language, daily manual-send cap.

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_social_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCampaigns per page.
offsetNoCampaigns to skip; use next_offset from the previous page.
client_idNoRestrict to one client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add context. It does so by enumerating the per-campaign payload — offer, platforms, cities with message language, daily manual-send cap — which is meaningful because there is no output schema. It stops short of noting ordering, total counts, or whether the send cap is a configured limit versus a consumed quota.

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?

A single front-loaded sentence with the platform scope first and the returned fields second. No filler, no restatement of the name or title, and every clause carries 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 three-parameter read-only list tool, the definition covers the two things an agent cannot get elsewhere: the platform-limited scope and the shape of the returned records (no output schema exists). It is only slightly short of complete because pagination behavior and the absence of filtering beyond client_id are left entirely to the schema.

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%, so limit, offset, and client_id are already fully documented in the schema, including the next_offset pagination hint. The description adds nothing about the parameters — not even that client_id is the way to narrow an otherwise cross-client listing — so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Return) plus a narrowly scoped resource: Instagram/TikTok/Facebook prospecting campaigns. The platform list separates it from a generic campaign lister, though it never names list_campaigns or list_outreach_campaigns as the non-social alternatives, so the boundary is inferred rather than declared.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. With siblings such as list_campaigns, list_outreach_campaigns, get_social_queue, and social_calendar in the catalog, the description gives no signal about which of these an agent should pick for a given request, and no prerequisites are stated.

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.