Skip to main content
Glama

ADS Beast

list_offer_packs

Read-only

Return the offer packs outreach copy is built from: built-in samples and this organization's own client packs, with brand, languages, niches, the facts the copy relies on and how many errors or warnings the last check found.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPacks per page.
offsetNoPacks to skip; use next_offset from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses a non-obvious behavior: the result set mixes built-in sample packs with the organization's own client packs, so agents know they cannot assume all results are user-created. It also reveals that each pack carries a prior validation result (error/warning counts), which hints at data freshness and quality state.

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 that leads with the action and the resource, then enumerates returned fields. The comma-list is dense but every clause carries information; no filler or restatement of the name.

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?

With no output schema, the description does the work of naming the returned fields (brand, languages, niches, facts, error/warning counts), which is exactly what an agent needs to plan a follow-up call. Only ordering and pagination behavior are left implicit, and offset semantics are covered by 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 and offset are already fully documented, including the next_offset paging hint. The description adds nothing about paging or default page size, so baseline 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 and resource ('Return the offer packs') and immediately scopes what a pack is ('outreach copy is built from'), plus the returned attributes. It does not name or differentiate against any sibling, but the siblings listed are unrelated list endpoints, so ambiguity is low.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the lookup step before building outreach copy, but the description never says when to call it versus other pack-related actions, nor does it note that no filtering by brand/language is available here.

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.