Skip to main content
Glama
nulab

Backlog MCP Server

by nulab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

update_pull_request

Update an existing pull request in Backlog: modify its summary, description, status, assignee, linked issue, or notify specific users.

Instructions

Updates an existing pull request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPull request number
repoIdNoRepository ID
issueIdNoIssue ID to link
summaryNoSummary of the pull request
repoNameNoRepository name
statusIdNoStatus ID
projectIdNoThe numeric ID of the project (e.g., 12345)
assigneeIdNoUser ID of the assignee
projectKeyNoThe key of the project (e.g., 'PROJECT')
descriptionNoUpdates an existing pull request
notifiedUserIdNoUser IDs to notify

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.15.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / organization
      Removed value: -{
-  "description": "Optional organization name. Use list_organizations to inspect available organizations.",
-  "type": "string"
-}
  2. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "Optional organization name. Use list_organizations to inspect available organizations.",
+  "type": "string"
+}
  3. Changed7 schema fields changedv1.0.0
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "The numeric ID of the project (e.g., 12345)",
+  "type": "number"
+}
    • removedInput schema / properties / projectIdOrKey
      Removed value: -{
-  "description": "Project ID or project key",
-  "type": [
-    "string",
-    "number"
-  ]
-}
    • addedInput schema / properties / projectKey
      Added value: +{
+  "description": "The key of the project (e.g., 'PROJECT')",
+  "type": "string"
+}
    • addedInput schema / properties / repoId
      Added value: +{
+  "description": "Repository ID",
+  "type": "number"
+}
    • removedInput schema / properties / repoIdOrName
      Removed value: -{
-  "description": "Repository ID or name",
-  "type": "string"
-}
    • addedInput schema / properties / repoName
      Added value: +{
+  "description": "Repository name",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "projectIdOrKey",
-  "repoIdOrName",
-  "number"
-]New value: +[
+  "number"
+]
  4. First observed

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Updates,' implying mutation, but does not state whether changes are reversible, require specific permissions, return the updated object, or affect related resources. This is completely opaque for a mutation tool.

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

Conciseness3/5

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

The description is a single, front-loaded sentence—concise and free of verbosity. However, it is so sparse that it under-specifies the tool's behavior, making it minimally adequate rather than a model of effective conciseness.

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

Completeness1/5

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

For an 11-parameter mutation tool with no output schema and no annotations, this description is severely incomplete. It does not explain what properties can be updated, what the response contains, any prerequisites, or how this tool fits into the broader workflow of managing pull requests.

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?

The schema covers all 11 parameters with descriptions (100% coverage), so the schema does the heavy lifting. The tool description adds no additional parameter meaning beyond stating the operation itself, which is redundant. Baseline 3 applies because the schema is sufficient.

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 'Updates an existing pull request' clearly states the verb (updates) and resource (pull request), making the core purpose unambiguous. However, it lacks any mention of which fields can be updated, which would further distinguish it from sibling tools like update_pull_request_comment or update_issue.

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 offers no guidance on when to use this tool versus alternatives, such as add_pull_request for creating a PR or update_issue for modifying issues. No prerequisites, exclusions, or recommended contexts are provided; usage can only be inferred as 'when you need to update a pull request,' which is tautological.

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/nulab/backlog-mcp-server'

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