Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitea: Create webhook

gitea_create_webhook
Destructive

Create a repository webhook to receive event notifications at a target URL, with configured events and optional secret or content type.

Instructions

[UNIFIED] Create a new webhook for a repository to receive event notifications.

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>",
      "url": "<url>",
      "events": "<events>"
    },
    "name": "gitea_create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
repoYes
siteYes
typeNogitea
ownerYes
activeNo
eventsYes
secretNo
content_typeNojson

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutation and non-idempotency profile is covered structurally. The description adds nothing beyond that: it does not say that a secret enables HMAC signing, that active defaults to true (so the hook fires immediately), that content_type controls payload format, or that repeated calls create duplicate hooks.

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 single sentence is front-loaded and free of filler, but its brevity is under-specification rather than economy for a 9-parameter destructive mutation tool.

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 9 parameters at 0% schema coverage, no output schema, and a destructive non-idempotent write, the description is far too thin for the tool's complexity. It leaves the agent without enough information to fill required fields like events or to understand the effect of secret and active.

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

Parameters1/5

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

Schema description coverage is 0% across 9 parameters, and the description compensates for none of it — url, events, secret, content_type, active, type and site are all left with bare types/defaults. Given a fully undocumented schema, the description carries the entire burden and supplies nothing.

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 ('Create a new webhook for a repository') plus its immediate effect ('to receive event notifications'), so the agent knows exactly what is produced. It does not distinguish this from sibling webhook tools such as gitea_update_webhook or gitea_test_webhook, and the '[UNIFIED]' prefix is left unexplained.

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 guidance on when to create a webhook versus updating, testing, or deleting one, nor on prerequisites such as admin/owner permissions on the repository. The agent must infer all usage context from the name 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