Skip to main content
Glama

ADS Beast

Agency Kit: everything about one client in one document

get_agency_kit
Read-only

The knowledge pack the agency keeps for one client: who they are, accounts and campaigns with the last 30 days of results, leads by stage, KPI goals, the write policy, the methodology of working through ADS Beast and ready prompts. Read it first when a conversation is about one client. Contains no contacts or keys.

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": {
      "client_id": "<client_id>"
    },
    "name": "get_agency_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYesClient id from list_clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely new behavior: results are bounded to the last 30 days, a write policy is embedded in the document, and contacts/keys are deliberately excluded. It does not disclose document size or how heavy the payload is, which matters for a 'one document' aggregate read.

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?

Two sentences, front-loaded with the core identity of the resource, then the contents inventory, then the usage rule and the exclusion. Every clause carries information; nothing is restated from the name or title.

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 must enumerate return contents and does so thoroughly, including the 30-day freshness window and what is absent (contacts, keys). The main residual gap is the shape/size of the returned document, which an agent calling an aggregate read would reasonably want.

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?

Only one parameter and schema description coverage is 100% ('Client id from list_clients'), so the schema already carries the semantics. The description adds only the framing that the id scopes the whole document; no format or validation detail beyond the schema.

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?

Uses a concrete noun phrase ('the knowledge pack the agency keeps for one client') plus an enumerated contents list, so the agent knows exactly what comes back: identity, accounts/campaigns with 30 days of results, leads by stage, KPI goals, write policy, methodology and prompts. It implicitly distinguishes itself from narrower siblings like get_client or get_campaign by being the single-client aggregate, though it names no sibling outright.

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?

"Read it first when a conversation is about one client" gives a clear trigger plus an ordering rule relative to the narrower per-entity tools. The clause 'contains no contacts or keys' usefully rules out a class of requests, but no explicit alternative is named for those cases.

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.