Skip to main content
Glama

Coline

Tag a file

tag_file
Idempotent

Adds a tag to a file, like project/launch. New tags join the workspace's tag list.

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": "tag_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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing a side effect not in the annotations: a previously unknown tag is created in the workspace's tag list as a consequence of tagging. It could still say more, e.g. what happens if the tag already exists.

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 short sentences, with the core action and its example front-loaded and the side effect stated second. Nothing is wasted or buried.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and annotations cover the mutation profile. For a 3-required-parameter mutation the description covers purpose, tag format, and tag-creation side effect; minor gaps remain around pre-existing tags and any tag-name constraints.

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 coverage is 67%; fileId and workspace are already documented in the schema as sourced from list_drive_files/search/fetch and workspaces.list. The description compensates for the undocumented tag parameter by supplying its expected shape and example ("project/launch"), which the schema lacks.

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 and resource ("Adds a tag to a file") and gives a concrete tag format example ("project/launch"), so the action is unambiguous. It does not distinguish itself from siblings such as save_tag, set_file_tags, or untag_file, leaving sibling routing to the reader.

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 usage is only implied: an agent can infer this is the incremental single-tag operation, but the description never names an alternative (save_tag, set_file_tags) or states when-not to use it. No prerequisites or exclusions are given.

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