AbleSign MCP

update_media_file

Partially update media file metadata, dates, or tags by providing the file ID and a set of changes.

Instructions

Partially update media metadata, dates, or tags.

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": {
      "media_file_id": "<media_file_id>",
      "changes": "<changes>"
    },
    "name": "update_media_file"
  }
}

Input Schema

Name	Required	Description	Default
`changes`	Yes
`media_file_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description mentions 'partial update' suggesting non-destructive behavior, but with no annotations, it fails to disclose other traits like permission requirements, idempotency, or how unspecified fields are handled. The behavioral profile is incomplete.

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?

The description is a single, front-loaded sentence that efficiently communicates the core function. It is appropriately sized for a simple tool but could benefit from a second sentence clarifying scope.

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?

Given the nested 'changes' parameter and 0% schema coverage, the description is insufficiently complete. It lacks details on valid properties, constraints, and behavioral context that the agent needs to use the tool correctly.

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 coverage is 0%, and the description only loosely groups 'metadata, dates, or tags' as valid change targets. It does not enumerate allowed keys or provide structure for the 'changes' object, leaving the agent to guess parameter semantics.

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 the tool updates media metadata, dates, or tags, using a specific verb and resource. It distinguishes from siblings like delete_media_file and upload/replacement tools, establishing a unique purpose.

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?

The description implies usage for partial updates but provides no explicit context on when to use, prerequisites, or alternatives. Without guidance on data validation or required existence of the media file, the agent must infer usage from context.

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

Deploy Server