Skip to main content
Glama

create_ticket

Create a ticket in a project. Use this whenever the user asks you to create, file, log or record a ticket (bug, backlog item, follow-up, feature request) for a project.

A ticket is a row in the project's "Tickets" datastore (columns Title, Description, Status, Priority, Created) on the project's protected Tickets page. This tool finds that page from any page in the project and creates the datastore with the standard columns if it does not exist yet.

Never write a ticket as a text, checklist or task block on the Tickets page: agents are rejected there, and such blocks do not appear in the ticket views.

Not for: items on the Agent Tasks list (add_ctlsurf_task_item), or Business change orders / proposals / SOWs (dashboard cards, load_toolset("dashboards")).

Put the full ticket body (problem, scope, acceptance criteria, links) in description as markdown.

Example: create_ticket(page_id="", title="Retry failed uploads", description="## Problem\n...", priority="High")

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": {
      "page_id": "<page_id>",
      "title": "<title>"
    },
    "name": "create_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort one-line ticket title (max 240 chars)
statusNoDefault Open
page_idYesAny page in the project: its Tickets page, the project root page, or any page under it. Find the root with find_page_by_root_path(root_path=<repo path>) if you have no page id.
priorityNoDefault Med
descriptionNoFull ticket body in markdown (max 10,000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the side effect that the Tickets page and datastore with standard columns are created if missing, and explains the rejection behavior for text/checklist blocks. It does not cover permissions, failure modes, or what the call returns, which is why it falls short of a 5 for a mutation tool with zero annotation coverage.

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 purpose, then definition, then anti-pattern, then exclusions, then parameter guidance, then a compact example. Every section earns its place, though the paragraph about the datastore/page mechanics is slightly dense and could be tightened without losing meaning.

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 mutation tool with no annotations and no output schema, the description covers what gets created, where it lands, the implicit datastore/page creation side effect, and how to populate the body. The main remaining gap is return behavior (e.g., whether a ticket id or link comes back), which an agent may need to chain into update_ticket.

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 schema already documents each parameter including enums and defaults (baseline 3). The description adds genuine meaning beyond the schema by instructing that the full ticket body (problem, scope, acceptance criteria, links) belongs in description as markdown, and the example demonstrates page_id/title/description/priority together in a realistic call.

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 and resource ('Create a ticket in a project') and then defines what a ticket physically is: a row in the project's Tickets datastore with columns Title, Description, Status, Priority, Created. It also explicitly excludes adjacent objects (Agent Tasks items, change orders/SOWs), so an agent can distinguish it from update_ticket or add_ctlsurf_task_item without opening schemas.

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 a clear triggering condition ('whenever the user asks you to create, file, log or record a ticket...') and an explicit 'Not for:' section routing to add_ctlsurf_task_item and the dashboards toolset. It even warns against a specific wrong approach (writing tickets as text/checklist/task blocks), which is a when-not that directly selects behavior.

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