Skip to main content
Glama
competlab

competlab-mcp-server

by competlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_ticket

Edit a ticket's title, description, labels, assignee, due date, effort, or impact, omitting fields to keep and sending a value to replace or null to clear. Does not change column.

Instructions

Change a ticket's title, description, labels, owner, due date, effort or impact. Omit a field to leave it as it is, send a value to replace it, and send null to clear it — except the description, cleared with an empty string, and the labels, cleared with an empty list, because for those an empty value is a real one. The column is never changed here: use move_ticket, so a ticket cannot change column as a side effect of an edit. Needs a read_write API key; a read key is refused and can only list and read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoThe ticket's title
effortNoHow much work the ticket is, or null to take it off
impactNoHow much the ticket matters, from 1 to 4 (1 Minor · 2 Moderate · 3 Significant · 4 Critical; 4 matters most), or null to take it off
dueDateNoThe day the ticket is due as YYYY-MM-DD, or null to take it off
labelIdsNoLabel IDs from the project's list. The list replaces what the ticket holds; an empty list clears them
ticketIdYesThe ticket's ID from list_tickets, or its number as a person writes it: '#14'
projectIdYesProject ID (from list_projects)
descriptionNoThe ticket's description, in Markdown. An empty string clears it
assigneeUserIdNoA current member's user ID (from list_ticket_assignees), or null to leave the ticket unassigned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.1

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries most of the burden and does add real value: auth requirement, refusal behavior for read keys, and the no-column-side-effect guarantee. However it does not describe what the mutation returns, whether edits are reversible/audited, or how label/assignee validation failures surface, so it stops short of full behavioral disclosure.

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?

Front-loaded with the field list and the core omit/value/null rule, and every sentence carries information (no filler). The middle sentence is a long dash-laden construction that takes a second read to parse, which costs it the top score.

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

Completeness5/5

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

For a 9-parameter mutation tool with no output schema and only minimal annotations, the description covers the write protocol, the exceptions, the auth scope, and the sibling routing. Nothing an agent needs in order to call this correctly is missing.

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 the per-parameter descriptions already carry the field-level detail (enums, ranges, formats). The description still adds the cross-cutting sentinel semantics — omit/value/null and the empty-string vs empty-list exceptions — which is meaning beyond what any single schema entry conveys.

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?

States a specific verb (change/update) and the exact mutable fields of the ticket resource, and explicitly distinguishes itself from move_ticket by declaring that column is never changed here. An agent can pick it over delete_ticket/move_ticket/create_ticket without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit rule for the field-presence protocol (omit = leave, value = replace, null = clear) plus the two documented exceptions, and names the alternative tool for column changes. It also states the precondition — a read_write API key, with read keys refused — so usage boundaries are unambiguous.

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