Skip to main content
Glama

Content assets

get_content_assets
Read-onlyIdempotent

Assets the swarm produced (image, video, copy, email) with their plan, status and prompt.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
plan_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds only the field list (plan, status, prompt) and content types; it says nothing about pagination, ordering, default retrieval size (the schema defaults limit to 30), or what happens when no plan_id is supplied.

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?

A single tight sentence with the resource and returned fields front-loaded and no filler. Its brevity is a structural strength even though the content is thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with two undocumented parameters and no output schema, the description leaves too much open: filtering by plan, result capping, and default page size are all unstated. It is not enough to let an agent call this correctly without inspecting the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both parameters (limit, plan_id) are undocumented in structured form and the description must compensate. It does not: 'with their plan' only loosely hints at plan association and never explains that plan_id filters results or that limit caps the result count up to 100.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (assets produced by the swarm) and even enumerates the content types (image, video, copy, email) plus returned fields (plan, status, prompt). However, it is a bare noun phrase with no verb, so it never explicitly says this is a retrieval/list operation, and it does nothing to distinguish itself from siblings like get_swarm_activity or list_plans.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to call this versus get_swarm_activity, list_plans, or get_content_item-style siblings, and no stated preconditions. The agent must infer usage purely from the name.

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