Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get an audience

get_audience
Read-onlyIdempotent

Retrieve a specific audience by ID to view its details for campaign targeting and management.

Instructions

Get an audience. Required API key scope: audiences:read. GET /audiences/{id}

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": {
      "id": "<id>"
    },
    "name": "get_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful context beyond that by naming the required API key scope (audiences:read), which tells the agent about an auth prerequisite. It does not cover failure behavior (e.g., nonexistent ID) or what fields an audience object returns.

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 short lines, front-loaded with the action and free of filler; the scope and endpoint details are easy to scan. Nothing is padded, though the terseness leaves the guidance gaps noted elsewhere.

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?

For a one-parameter read tool with annotations and no output schema, the definition is close to adequate: what the tool retrieves and what auth it needs are clear. It omits the shape of the returned audience and error conditions, which an agent may need for planning but can partly discover at call time.

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% and there is only one parameter, so baseline is 3. The description's 'GET /audiences/{id}' minimally confirms the id is a path parameter identifying an audience, but adds no format, source, or discovery guidance beyond what the schema property already states.

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

Purpose3/5

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

The description restates the title almost verbatim ("Get an audience"), but the appended 'GET /audiences/{id}' does clarify that this is a single-resource fetch by identifier rather than a listing. It stops short of distinguishing itself from siblings such as list_audiences or list_audience_members beyond the implicit singular/plural split.

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 explicit when-to-use guidance: nothing says to call this when you have an audience ID and need full details, versus list_audiences for enumeration. No prerequisites, no exclusions, and no named alternatives are given, leaving routing entirely to inference.

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

Deploy Server

Other Tools