Skip to main content
Glama

Suggest audiences (onboarding step 3)

suggest_audiences

Step 3 («Кому пишем»): three customer profiles (ICP) to search for, from the company and the goal; each with a short title, the profile text and why. The chosen text is the icp of create_search. Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/audiences]

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": {
      "company": "<company>",
      "goal": "<goal>"
    },
    "name": "suggest_audiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
companyYes
onboarding_idNoThe onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the same new search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false) already mark this as a non-safe, non-repeatable state-creating call; the description adds real value beyond them by disclosing that the call consumes the single brief quota and that it returns an onboarding_id that must be threaded into later calls. It still does not say what happens if the quota is exhausted or whether suggestions are persisted before create_search.

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?

The step number and step label are front-loaded, then return shape, then the data-flow instruction, then the endpoint tag — a sensible order with little waste. The parenthetical quota sentence is dense but earns its place; the Cyrillic step label and REST tag add mild noise for non-Russian agents.

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, no-output-schema tool it covers what the agent needs: inputs, returned profile structure, and the onboarding_id threading that links it to create_search. Remaining gaps are edge behavior (quota exhaustion, failure modes, whether profiles can be refined) rather than anything required to make a correct first call.

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 onboarding_id has schema documentation (33% coverage); the description partially compensates by framing company and goal as the two inputs that generate the ICPs, but it gives no expected format, granularity, or length guidance for them despite maxLength bounds of 5000 and 2000. onboarding_id semantics are fully covered by the schema, so the description adds meaning mainly for the two undocumented fields.

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?

"Three customer profiles (ICP) to search for, from the company and the goal" names a specific verb-equivalent action (suggest), the exact resource (ICP profiles), and the inputs that drive it. It also states the concrete return shape (short title, profile text, why) and ties the result to create_search's `icp`, so it is distinguishable from suggest_goals or suggest_company_description without opening schemas.

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?

It states the placement in the workflow (onboarding step 3, first assistant call of an onboarding) and gives a hard constraint: one brief per onboarding, each assistant callable once on a free account. What it does not do is name sibling steps as explicit alternatives or spell out when not to use it (e.g. when editing an existing search), but the sequencing guidance is clear enough to act on.

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.

Resources