Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Update Workspace Job

update_workspace_job

Update an existing workspace job by modifying its name and node inclusion/exclusion selectors.

Instructions

Update an existing workspace job.

Args:

  • workspaceID (string, required): The workspace ID

  • jobID (string, required): The job ID

  • name (string, required): Updated job name

  • includeSelector (string, required): Node selector. Format: '{ location: LOC name: NAME } OR { location: LOC name: NAME }'

  • excludeSelector (string, required): Node exclusion selector. Same format as includeSelector

Returns: Updated job object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUpdated name for the job
jobIDYesThe job ID to update
workspaceIDYesThe workspace ID
excludeSelectorYesNode exclusion selector string. Same format as includeSelector. Use empty string to exclude nothing.
includeSelectorYesNode selector string. Format: '{ location: LOC name: NAME } OR { location: LOC name: NAME }'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
messageNo
Behavior2/5

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

Annotations already indicate non-readonly, non-destructive, and non-idempotent. Description adds minimal behavioral detail beyond stating it updates and returns an object.

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

Conciseness4/5

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

Fairly concise, front-loaded with the main purpose. Uses a clear list format for parameters, but could be slightly more efficient.

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

Completeness3/5

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

Basic purpose and parameters are covered; output schema exists so return details are optional. Lacks usage context and differentiation from sibling tools, making it minimally complete for a 5-param tool.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. Description repeats parameters and adds minor format hints for selectors, but does not significantly enhance understanding beyond schema.

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?

Clearly states the action 'Update' and the resource 'existing workspace job'. Distinguishes from sibling tools like create_workspace_job and delete_workspace_job.

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?

No guidance on when to use versus alternatives, no prerequisites mentioned, and no conditions for use provided.

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/Coalesce-Software-Inc/coalesce-transform-mcp'

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