Skip to main content
Glama
CainDez
by CainDez

gitee_update_webhook

Update a webhook configuration for a Gitee repository, specifying payload URL, events, and encryption settings.

Instructions

Update a webhook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner
repoYesRepository path name
idYesWebhook ID
urlYesPayload URL
encryption_typeNoEncryption type
passwordNoPassword or secret
push_eventsNoPush events
tag_push_eventsNoTag push events
issues_eventsNoIssues events
note_eventsNoComment events
merge_requests_eventsNoPR events
Behavior1/5

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

No behavioral details beyond the verb 'Update'. No mention of side effects, permissions required, return value, or idempotency. This is insufficient for a mutation tool with no annotations.

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 sentence, which is concise but lacks essential content. It earns its place but could be expanded without losing brevity.

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?

With no output schema, no annotations, and 11 parameters, the description fails to provide context about the operation's effects, prerequisites, or success criteria. Highly incomplete.

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 coverage is 100% with each parameter described. The description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 states 'Update a webhook', which clearly indicates the action and resource. It distinguishes from create, delete, get, list, and test webhooks among siblings.

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?

No guidance on when to use this tool vs alternatives like create_webhook, delete_webhook, or test_webhook. The description does not mention that it modifies existing webhooks or what parameters are typically changed.

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/CainDez/mcp-gitee'

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