Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Update pull request

gitea_update_pull_request
Destructive

Update an existing Gitea pull request by changing its title, body, state, assignees, labels, or milestone.

Instructions

[UNIFIED] Update an existing pull request. Can modify title, body, state, assignees, labels, and milestone.

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": {
      "site": "<site>",
      "owner": "<owner>",
      "repo": "<repo>",
      "pr_number": "<pr_number>"
    },
    "name": "gitea_update_pull_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
repoYes
siteYes
ownerYes
stateNo
titleNo
labelsNo
assigneeNo
assigneesNo
milestoneNo
pr_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so file description need not restate the mutation risk. What it adds is the field inventory, but it omits important behavior: whether omitted fields stay unchanged, whether labels/assignees replace or append, and whether required permissions exist.

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?

Two compact sentences, front-loaded with the verb and resource, with no padding. The '[UNIFIED]' prefix is minor noise but nothing is redundant.

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 destructive 11-parameter mutation tool with no output schema and no schema descriptions, the description leaves too much unexplained: replacement semantics for list fields, the assignee/assignees ambiguity, state transition rules, and how the PR is identified via site/owner/repo/pr_number.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description must carry the semantics and it does not. It merely lists the field names, without explaining accepted formats (labels string vs list), the allowed 'state' values, or the difference between the duplicate 'assignee' and 'assignees' parameters.

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 names a specific verb and resource ('Update an existing pull request') and enumerates the mutable fields, which helps distinguish it from close/reopen/merge siblings. It stops short of explicitly stating which sibling to use for each alternative operation.

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?

There is no when-to-use guidance, no alternatives named, and no note that changing 'state' overlaps with gitea_close_pull_request and gitea_reopen_pull_request. An agent must infer from sibling names alone that close/reopen are preferred for state transitions.

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