Skip to main content
Glama
Sign In
Picsha AI MCP Server

Picsha AI MCP Server

Official
by picsha-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

update_asset

Update an asset's name, tags, or custom metadata. Add tags normally or remove them by prefixing with a hyphen.

Instructions

Update an asset's tags or custom metadata. Prefix a tag with a hyphen (e.g. '-discard') to remove it, or specify normally to add 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": {
      "id": "<id>"
    },
    "name": "update_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe unique ID of the asset
nameNoOptional new name/title for the asset
tagsNoArray of strings to append as tags. Prefix with a hyphen to remove.
metadataNoCustom key-value dictionary to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.12

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided. Description covers tag removal syntax but lacks details on behavior for name updates, metadata merging, permissions, or side effects.

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 with front-loaded purpose and no filler. Every sentence adds value.

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?

Missing behavioral details for a mutation tool with 4 parameters, nested objects, and no output schema. Incomplete guidance on name updates and metadata handling.

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 covers all parameters. Description adds value by explaining tag prefix syntax for removal, but does not elaborate on 'name' or 'metadata' beyond schema.

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

Purpose5/5

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

The description clearly states 'Update an asset's tags or custom metadata,' specifying the verb and resource. It distinguishes from sibling tools like 'delete_asset' and 'get_asset'.

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 specific syntax for adding/removing tags, but no guidance on when to use this tool versus alternatives like 'summarize_asset' or 'moderate_asset'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools