Skip to main content
Glama

Read a connected creative source

playground_connected_source_read
Read-onlyIdempotent

Execute one allowlisted read with the exact connected account ID and discovered tool version. Returns bounded source data and a receipt; no external write or export is possible. Returns bounded source data, a provenance receipt and an optional next-page token.

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": {
      "projectId": "<projectId>",
      "accountId": "<accountId>",
      "operationId": "<operationId>",
      "version": "<version>"
    },
    "name": "playground_connected_source_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesExact version returned by discovery for the selected operation or skill.
accountIdYesConnected account ID returned by connected_sources_list.
argumentsNoArguments for the selected connector operation, matching connected_source_schema.inputSchema.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
operationIdYesRead operation ID returned by connected_sources_list; inspect its schema before supplying arguments.

Output Schema

NameRequiredDescriptionDefault
dataYesBounded data in the selected connector operation’s native format.
nextPageTokenNo
sourceReceiptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds real context beyond them: reads are restricted to an allowlist, 'no external write or export is possible', and results include a provenance receipt and optional next-page token. That is meaningful behavioral disclosure. The only miss is any note on failure conditions when the account or version is stale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the description wastes a full clause repeating itself: 'Returns bounded source data and a receipt' is immediately restated as 'Returns bounded source data, a provenance receipt and an optional next-page token.' Consolidating the two sentences would lose nothing and remove visible redundancy.

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?

With a populated output schema, the description needn't explain return values, and annotations cover the safety profile, so what remains is scope and prerequisites — both present, including the read-only allowlist constraint. It is nearly complete for a tool of this complexity; only error/staleness behavior is unstated.

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 description coverage is 100%, so accountId, version, operationId, projectId and the free-form arguments bag are all documented in the schema itself. The description only echoes that the account ID and version must be exact and discovered, adding little beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description uses a specific verb and scope: 'Execute one allowlisted read with the exact connected account ID and discovered tool version.' It makes clear this performs a single read against a connected creative source, distinguishishable from discovery/schema siblings. It stops short of naming a sibling to route away from (e.g. connected_sources_list or connected_source_schema), so differentiation is implied rather than explicit.

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 context is implied through prerequisites ('exact connected account ID', 'discovered tool version'), which tells the agent it must run discovery first. However, there is no explicit when-to-use vs. when-not, and no mention of alternatives such as the schema or list tools that supply those IDs and versions. An agent can infer the workflow but not the boundaries.

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.