Skip to main content
Glama

Coline

Untag a file

untag_file
Idempotent

Takes a tag off a file.

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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>",
      "tag": "<tag>"
    },
    "name": "untag_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
fileIdYesFile or folder id from list_drive_files, search or fetch.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
tagsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered structurally. The description adds no behavioral context of its own — no note that removing a nonexistent tag is a no-op, no permission or sharing implications, nothing about effects on other collaborators' tags.

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

Conciseness3/5

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

A single clause with no padding, so there is nothing extraneous to trim, but it is radically under-specified rather than concise — the brevity comes at the cost of any useful information.

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?

Output schema exists so return values need not be described, and annotations carry the safety profile. Still, for a three-parameter mutation tool the definition omits how tag matching works and what happens when the tag is absent, leaving the agent to guess at call correctness.

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 67% (workspace and fileId documented, tag not), so the description should compensate but instead only implies 'file' and 'tag' with no format, case-sensitivity, or tag-identifier guidance, and never mentions the required workspace slug. It adds essentially zero meaning beyond the 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?

"Takes a tag off a file" restates the tool name and title (untag_file / Untag a file) without adding a sharper verb, scope, or any differentiation from siblings such as tag_file, set_file_tags, or list_file_tags. An agent learns nothing beyond what the identifier already told it.

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: nothing says this removes a single tag versus replacing the whole tag set (set_file_tags), nor what to do if the tag is not present. The agent must infer the alternative from sibling names, which the instructions say not to rely on.

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