Skip to main content
Glama
lstpsche

@lstpsche/apidog-mcp

by lstpsche

apidog_bulk_update

Batch update Apidog endpoints by applying tags, folder, status, or summary changes. Target endpoints explicitly or by filters, and preview modifications before applying with confirm=false.

Instructions

Batch update endpoints. Target by explicit endpoints array OR keyword filters. Supports: addTags, removeTags, setFolder, setStatus, setSummaryPrefix, summaryFindReplace. Set confirm=false to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleYesModule name
addTagsNoTags to add
confirmNoSet true to apply, false/omit to preview
projectNoProject name. Required when multiple projects are configured, optional otherwise.
endpointsNoExplicit list of endpoints to update (alternative to filters)
filterTagNoFilter by tag name
setFolderNoSet x-apidog-folder (empty string to clear)
setStatusNoSet x-apidog-status (designing, pending, developing, testing, released, deprecated, obsolete)
filterPathNoFilter by path substring
removeTagsNoTags to remove
filterFolderNoFilter by folder name
filterMethodNoFilter by HTTP method
filterStatusNoFilter by x-apidog-status
setSummaryPrefixNoPrefix to add to summaries (idempotent)
summaryFindReplaceNoFind/replace in summaries
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states 'Set confirm=false to preview,' warning against accidental mutations, and enumerates supported operations. It lacks details on auth or side effects, but the preview mechanism is a key safety behavior.

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 and a compact list deliver high information density without fluff. The most important details are front-loaded: batch update, targeting modes, supported operations, and preview safety.

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?

For a 15-parameter tool with nested objects and no output schema, the description provides a solid high-level overview including target selection and preview mode. It does not describe the preview output format or operation interactions, but the rich schema covers parameter-level details.

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 100%, so a baseline of 3 applies. The description adds value beyond the schema by clarifying the OR relationship between endpoints and filters and by emphasizing the confirm flag's role in previewing. This elevates it above baseline.

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 opens with 'Batch update endpoints,' clearly specifying the action, resource, and scope. The list of supported operations and targeting modes further distinguishes it from sibling tools like apidog_update, which is singular in nature.

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

Usage Guidelines4/5

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

The description explains how to target endpoints (explicit array OR keyword filters) and mentions the preview mode, giving clear operational guidance. It does not explicitly name alternatives or exclusions, but 'batch' strongly implies when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lstpsche/apidog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server