Skip to main content
Glama
Sign In
bbkt

bbkt

by zach-snell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

manage_issues

List, get, create, and update repository issues with filtering, assignment, priority, state, and kind options.

Instructions

Unified tool for managing repository issues (list, get, create, update)

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": {
      "action": "<action>",
      "workspace": "<workspace>",
      "repo_slug": "<repo_slug>"
    },
    "name": "manage_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoIssue kind: bug, enhancement, proposal, task (for 'create', 'update')
pageNoPage number
queryNoFilter query (for 'list')
stateNoIssue state: new, open, resolved, on hold, invalid, duplicate, wontfix, closed (for 'list', 'create', 'update')
titleNoIssue title (for 'create', 'update')
actionYesAction to perform: 'list', 'get', 'create', 'update'
contentNoIssue description content (for 'create', 'update')
pagelenNoResults per page
assigneeNoAccount ID of the user assigned to the issue (for 'create', 'update')
issue_idNoIssue ID (for 'get', 'update')
priorityNoIssue priority: trivial, minor, major, critical, blocker (for 'create', 'update')
repo_slugYesRepository slug
workspaceYesWorkspace slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the four action types but doesn't describe what each action does, what permissions are required, whether operations are idempotent, rate limits, or what happens on success/failure. 'Manage' is vague about mutation behaviors.

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?

The description is a single, efficient sentence that states the unified nature and four action types. It's appropriately sized for a multi-action tool, though it could be more front-loaded with key behavioral context given the lack of annotations.

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

Completeness2/5

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

For a complex 13-parameter mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'manage' entails for each action, what values are returned, error conditions, or how this tool fits with sibling tools. The agent lacks crucial context for proper invocation.

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 description coverage is 100%, so the schema already documents all 13 parameters thoroughly with descriptions and action mappings. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as a 'unified tool for managing repository issues' with specific actions (list, get, create, update). It distinguishes itself from siblings like manage_commits or manage_pull_requests by focusing on issues, but doesn't explicitly differentiate from other issue-related tools that might exist.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose specific actions, or how it relates to sibling tools like manage_repositories or manage_workspaces. The agent must infer usage from the action parameter alone.

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