Skip to main content
Glama

Read current creative output feedback

playground_output_feedback_list
Read-onlyIdempotent

Read this user’s accept/change verdicts for media still attached to the Playground project. Requires project view access. Returns recorded output feedback for the project.

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_output_feedback_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
feedbackYes
truncatedYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them: an authorization requirement (project view access) and two filters ('this user's' verdicts, only media 'still attached'). However it says nothing about pagination, ordering, or what happens to feedback for detached media, so the extra context is useful but partial.

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?

Three short sentences, front-loaded with the action and scope, no filler. The final sentence ('Returns recorded output feedback for the project') largely restates the first and is the only soft 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?

A simple, non-destructive read with a rich output schema, 100% parameter coverage, and full annotation coverage — so return format and safety need no prose. What remains missing is only guidance relative to sibling list tools; everything needed to call it correctly is present.

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?

A single required projectId at 100% schema description coverage, and the schema already explains both format and provenance ('obtain it from project creation, an explicit project link or current context'). The description says 'the Playground project' but adds no syntax, format, or failure-mode detail beyond the schema, so 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?

Specific verb 'Read' plus a precisely scoped resource: 'this user's accept/change verdicts for media still attached to the Playground project.' That scoping (current user, still-attached media) makes the tool distinguishable in substance, though it never names the nearest sibling (e.g. playground_approvals_list) to contrast against.

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?

Provides a clear precondition ('Requires project view access') and the implied context of reading feedback for a chosen project, but gives no explicit when-to-use vs. when-not, and does not route the agent away from adjacent list tools such as playground_approvals_list. Usage is inferable rather than stated.

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.