Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-bulkAssign

Idempotent

Assign multiple tags to a Dokploy project in one request using the project ID and tag IDs, simplifying bulk tag management.

Instructions

POST /tag.bulkAssign

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": {
      "projectId": "<projectId>",
      "tagIds": "<tagIds>"
    },
    "name": "tag-bulkAssign"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the description's only contribution is the word 'POST', which weakly signals a write operation. It says nothing about what gets written, whether assignments are additive or replace existing tags, or what authorization is required — context an agent needs for a bulk mutation.

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?

It is short, but brevity here reflects under-specification rather than economy — a bare route string that is not front-loaded with any actionable information.

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 bulk mutation tool with two undocumented required parameters, no output schema, and no explanatory text is entirely inadequate. Nothing about effect, scope, or result is communicated.

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% and there are two required parameters, projectId and tagIds, neither explained in the description. The agent must guess that tagIds accepts an array of tag identifiers and how the project scoping applies.

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?

The description is only the HTTP route 'POST /tag.bulkAssign', which restates the tool name rather than explaining the operation. The name alone hints at bulk tag assignment, but the description adds no verb-and-resource statement of its own, and nothing distinguishes it from siblings like tag-assignToProject or tag-removeFromProject.

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 guidance on when to use this tool versus tag-assignToProject or tag-removeFromProject, no mention of prerequisites, and no exclusions. The agent is left to infer everything from the route string.

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