Skip to main content
Glama

speechify_move_item

Move a Speechify file or folder to a new parent, using an idempotency key and expected version to prevent duplicate or conflicting changes.

Instructions

Perform verified Speechify move item.

Input Schema

NameRequiredDescriptionDefault
nameNo
item_idNo
if_existsNoerror
parent_idNo
idempotency_keyYes
expected_updated_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the entire burden, yet it discloses nothing about side effects, permission requirements, or what happens to the item's prior parent. The presence of idempotency_key and expected_updated_at signals retry/concurrency semantics that the description never explains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words, but it is concise to the point of under-specification; there is no front-loaded statement of effect or scope because there is essentially no content.

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

Completeness1/5

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

A 6-parameter mutation tool with no annotations and no output schema needs a substantive description of preconditions and effects, and this one provides none beyond echoing the name.

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

Parameters1/5

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

Schema description coverage is 0% across 6 parameters, and the description adds no meaning for item_id, parent_id, if_exists, expected_updated_at, or the required idempotency_key. Nothing compensates for the undocumented schema.

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

Purpose2/5

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

"Perform verified Speechify move item" restates the tool name plus an unexplained qualifier ("verified"); it names no source/destination semantics and gives no basis for distinguishing this move from siblings such as speechify_rename_item or speechify_trash_item.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the 16 sibling tools; an agent must guess whether moving is the right operation versus renaming or re-parenting.

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