Shager

Set who accounts speak to

set_audience

Idempotent

Set the market of accounts or groups: the countries they speak to, the whole world, and/or one time zone. get_best_times times each account for its market (an account's own wins over its groups'; an account in several groups gets all their countries). Use it when a workspace's accounts or groups serve different markets, e.g. one group for the US and one for Israel, or a group for everyone. clear: true removes the market, so Shager goes back to where the clicks come from.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "set_audience"
  }
}

Input Schema

Name	Required	Description
`clear`	No	true: remove the market
`world`	No	true: everyone, worldwide (instead of countries)
`timezone`	No	IANA zone, when one zone fits the audience
`countries`	No	Two-letter countries, e.g. ["US","GB"]
`group_ids`	No	Groups to set (from list_groups)
`channel_ids`	No	Accounts to set (from list_channels)
`workspace_id`	Yes	Workspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description explains important behavioral effects: clear: true removes the market, timing falls back to click-derived behavior, an account's own market wins over its groups', and an account in multiple groups inherits all their countries. This adds meaningful operational context for a non-destructive but mutating tool.

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 description is front-loaded with the purpose and stays focused, though the explanation of get_best_times timing and the Shager fallback adds some length. Overall it is efficient for a seven-parameter mutation tool.

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?

Given full schema coverage and rich annotations, the description provides enough context to invoke the tool correctly. It could be slightly more explicit about combined use of account and group IDs or expected confirmation behavior, but those gaps are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter well. The description still adds useful interaction semantics, especially the precedence rule between an account's own market and its groups, and how multiple group memberships combine countries.

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?

The description states a specific verb and resource: setting the market of accounts or groups, covering countries, worldwide, and timezone. It clearly distinguishes the operation from sibling tools like get_best_times by explaining the relationship between audience definition and timing.

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 gives an explicit usage condition and concrete examples, such as one group for the US and one for Israel or a group for everyone. It does not name a competing alternative for setting audiences, but its when-to-use guidance is clear and actionable.

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

All Shager tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?