Skip to main content
Glama

Explore Berrys editing actions

playground_actions_discover
Read-onlyIdempotent

Discover implemented media editing and canvas actions. No project needed to browse; include projectId to check its permissions. By default, omit unavailable actions. Does not inspect a canvas, enable a feature, edit media or spend credits. Follow each action’s tool schema when applying it. Returns matching actions with availability and requirements.

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": "playground_actions_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch words describing the item or content to find.
projectIdNoID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
includeUnavailableNoWhether to include actions that are currently unavailable, together with their availability reasons.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
actionsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower. The description still adds real value: no credit spend, no canvas inspection, no feature enabling, permission-aware results when projectId is supplied, and the instruction to follow each action's own tool schema.

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?

Five tight sentences, each doing distinct work: purpose, project scoping, default filtering, non-effects, and follow-up guidance. No padding or repeated schema text.

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 an output schema present, the description needn't explain return values, and it still notes that results carry availability and requirements. Combined with the exclusions and permission note, an agent has enough to call it correctly; only the lack of explicit alternative-tool routing leaves a small gap.

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 baseline is 3. The description goes slightly beyond it by explaining what projectId actually does (checks that project's permissions) and by restating the includeUnavailable default as an omission behavior, tying the parameters to observable outcomes.

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 opens with a specific verb+resource: "Discover implemented media editing and canvas actions." Negative scoping ("does not inspect a canvas, enable a feature, edit media or spend credits") further pins down what this is not, which helps separate it from canvas/media siblings. It never names the closest discovery siblings (capabilities/skills discover), so differentiation there 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"No project needed to browse; include projectId to check its permissions" gives an explicit condition for the only meaningful optional parameter, and "By default, omit unavailable actions" states the default behavior. It stops short of telling the agent when to prefer this over other discovery tools.

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.