Skip to main content
Glama

Samuelz® Marketing

Marketing-Verbindungen lesen

list_marketing_connections
Read-onlyIdempotent

List current tenant-bound marketing resources and supported reporting functions without credentials. Requires marketing:read and current Marketing module read access. Connection identity does not prove live provider access. OpenAI Ads reports require explicit, current credential-bound report consent; account identity alone is insufficient. POST /api/v1/tenant/read/list_marketing_connections.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_marketing_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description adds real value beyond them: connection identity does not prove live provider access, and OpenAI Ads reports need explicit current credential-bound consent. This pre-empts a costly misinterpretation of the returned data. It stops short of describing the shape or granularity of the listing (per-connection fields, whether capabilities are nested).

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?

Front-loaded with the operation and scope, then permissions, then the important semantic caveat — good ordering with no filler sentences. The trailing internal route "POST /api/v1/tenant/read/list_marketing_connections" adds little for tool selection and is slightly at odds with an idempotent read, but it is only a few words.

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 zero-parameter, no-output-schema tool, the description should convey what the returned list actually contains; "marketing resources and supported reporting functions" is directional but vague about per-item fields and whether it covers a single tenant or all bound connections. Permissions and consent caveats are well handled, so the gap is limited to return-value expectation setting.

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?

Zero parameters, so the baseline of 4 applies; there is no parameter meaning to add or omit. No description text is needed here and none is wasted.

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?

"List current tenant-bound marketing resources and supported reporting functions" gives a specific verb (list) plus a dual object (connections + supported reporting functions), so the agent knows this is a discovery/enumeration tool rather than a data-fetch. It does not name or contrast with the closest siblings (get_marketing_setup, list_capabilities), so the boundary is left to inference.

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?

Prerequisites are stated clearly (marketing:read plus current Marketing module read access), which tells the agent when the call will fail, and the "without credentials" framing implies pre-flight discovery. However, there is no explicit when-to-use vs. when-not, and no routing to get_marketing_setup or list_capabilities, which appear to overlap in intent.

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