Skip to main content
Glama

uploadcare

by io.usefulapi

List webhooks

uploadcare_list_webhooks
Read-only

List all webhook subscriptions configured for the project. REST API: GET /webhooks/.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and description adds REST endpoint GET /webhooks/. No additional behavioral traits (e.g., pagination) are mentioned, but for a simple list with no params, this is adequate.

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

Conciseness5/5

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

Two short, clear sentences with no wasted words. Front-loaded with purpose, then REST endpoint.

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

Completeness5/5

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

Given no parameters, simple list operation, and read-only annotation, the description is complete enough. No output schema needed for clarity.

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

Parameters4/5

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

No parameters exist, so baseline is 4. Description adds no parameter info, which is fine.

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

Purpose5/5

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

Clearly states it lists all webhook subscriptions. Verb 'List' and resource 'webhook subscriptions' are specific. Differentiates from sibling 'uploadcare_create_webhook'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not, but the purpose is clear and siblings are distinct operations. The simplicity of a list operation makes alternatives obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All uploadcare toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (e.g., create webhook vs. delete file vs. get group). No two tools overlap in purpose, making it easy for an agent to select the correct one.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: uploadcare_create_webhook, uploadcare_delete_file, etc. This predictability helps agents infer tool functions from names.

Tool Count5/5

With 11 tools, the server covers key areas (files, groups, webhooks, project) without being overwhelming. The count is well-scoped for a file management service.

Completeness3/5

The tool set covers core file operations (get, delete, list, store, upload) but has gaps: missing update/delete for webhooks, create/delete for groups, and update for files. These omissions may force agents to use workarounds.

Resources