GTM Daily

Get a GTM agency

get_gtm_agency

Read-onlyIdempotent

Full public profile of a published agency or consultant by slug or 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": {
      "agency_id_or_slug": "<agency_id_or_slug>"
    },
    "name": "get_gtm_agency"
  }
}

Input Schema

Name	Required	Description	Default
`agency_id_or_slug`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`data`	No
`status`	Yes
`message`	No
`warnings`	No
`next_step`	No
`next_cursor`	No
`action_grant`	No
`approval_url`	No
`correlation_id`	Yes
`missing_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds one genuine behavioral detail — 'published' implies unpublished or unknown slugs return nothing — but says nothing about what happens on a miss or how much data 'full' entails.

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?

One sentence, no waste, with the resource and the accepted key forms front-loaded. Nothing in it is redundant with the 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?

For a one-parameter read with an output schema and full annotation coverage, very little is required. The output schema carries the return shape and the annotations carry the semantics; only failure behavior for unpublished agencies is left unstated.

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 0%, so the description must carry the burden, and it does the important part: 'by slug or id' tells the agent the single string parameter accepts two identifier forms, which the bare schema (string, maxLength 200) does not reveal. It does not give format or example values.

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 resource and scope: 'full public profile of a published agency or consultant', with the lookup key named ('by slug or id'). The word 'full' distinguishes it from the listing sibling search_gtm_agencies, though that sibling is never named explicitly.

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: the agent must infer this is the detail-fetch step that follows a search_gtm_agencies result. There is no explicit when-to-use, no statement that it should be called with an id obtained from search, and no exclusion of alternatives.

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

All GTM Daily 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?