Skip to main content
Glama

Edit an asset

update_content_asset

Change an existing asset's caption, hashtags or review status (draft/approved/rejected). Use this to correct generated copy instead of regenerating it.

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": {
      "item_id": "<item_id>"
    },
    "name": "update_content_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoHuman review decision for this asset
captionNo
item_idYes
hashtagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered and the description adds the useful 'edit in place, don't regenerate' framing. However, it does not disclose partial-update semantics — only item_id is required, and it never says whether omitted fields are preserved or overwritten, which matters for a non-idempotent mutation.

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?

Two sentences, zero filler, with the editable-field scope front-loaded before the usage rule. Every clause carries information.

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

Completeness3/5

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

For a four-parameter, one-required mutation with no output schema, the description covers what can change and why, but leaves the agent guessing about partial-update behavior, item_id semantics, and whether the response returns the updated asset. These gaps are meaningful given the thin schema coverage.

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 coverage is only 25%: caption, hashtags and item_id carry no schema descriptions. The description partially compensates by naming the three editable fields and the draft/approved/rejected status values, but it repeats what the enum already encodes and says nothing about item_id's role or hashtag/caption constraints.

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 ('Change') and resource ('existing asset') and enumerates the three mutable fields (caption, hashtags, review status), so the agent knows exactly what surface is touched. It does not explicitly name a sibling such as create_content_item or get_content_assets, so differentiation is implied rather than stated.

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?

Gives an explicit when-to-use rule: correct generated copy rather than regenerating it, which routes the agent away from a regeneration path. It stops short of stating exclusions, e.g. that it cannot create assets or change item identity, and gives no prerequisites or permission context.

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