Skip to main content
Glama

List connected creative sources

playground_connected_sources_list
Read-onlyIdempotent

List active Drive, Shopify, Meta Ads, and Gmail accounts and read-only operation names. Uses the signed-in user’s connected accounts and project access. Returns connected accounts and available read operations.

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>"
    },
    "name": "playground_connected_sources_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
accountsYes
operationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is to add scoping context. It does add that results are limited to the signed-in user's connected accounts and project access, but it says nothing about what happens when a provider is unconnected or how operation names are scoped — modest value on top of rich annotations.

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 resource and the provider list in the first sentence. The third sentence largely restates the first ('Returns connected accounts and available read operations'), making it slightly redundant, but the overall length is appropriate.

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?

A simple single-parameter, read-only list with an output schema, so the description does not need to explain return shapes. It covers providers, account scoping, and that operation names are read-only; only the empty/unconnected-provider behavior is left unstated, which is minor here.

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 one parameter (projectId) exists and the schema documents it fully with format, pattern, and a description explaining where to obtain it. The prose adds no additional meaning about projectId, so the schema does all the work and the baseline 3 applies.

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 verb (list) and resource (active connected accounts across Drive, Shopify, Meta Ads, Gmail) plus read-only operations, which is concrete enough to distinguish it from the deeper siblings like playground_connected_source_read. It stops short of naming why you'd pick this over playground_connected_source_schema, so it is clear but not sibling-differentiating.

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 implied rather than stated: the sentence about using the signed-in user's connected accounts and project access hints at prerequisites, and the enumeration of providers suggests it is a discovery call before reading. There is no explicit when-to-use, when-not-to-use, or pointer to the read/schema siblings that would consume the returned operation names.

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.