Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

create_webhook

Subscribe to webhook notifications from the Approved Platform and receive POST callbacks when invoice flows matching your filters are created or updated.

Instructions

Subscribe to webhook notifications from the Approved Platform.

The AP will POST event payloads to the callback URL whenever a flow matching the specified filters (flow type, direction, processing rule, ack status) is created or updated.

HUMAN-IN-THE-LOOP: Requires user confirmation. Call without confirmation_token first, show the summary to the user, then call again with the token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_typeNoAuthentication type for the callback: BASIC or OAUTH2.
flow_typeYesFlow type to subscribe to: CustomerInvoice, SupplierInvoice, CustomerInvoiceLC, SupplierInvoiceLC, AggregatedCustomerTransactionReport, UnitaryCustomerTransactionReport, AggregatedCustomerPaymentReport, UnitaryCustomerPaymentReport, UnitarySupplierTransactionReport, MultiFlowReport, StateInvoice, StateCustomerInvoiceLC, StateSupplierInvoiceLC.
ack_statusNoOptional acknowledgement status filter: Pending, Ok, Error.
auth_user_idNoUser ID for BASIC authentication on the callback URL.
callback_urlYesURL the Approved Platform will POST notifications to. Must be HTTPS and reachable from the AP network.
signature_keyNoBase64-encoded signing key for webhook payload verification.
auth_client_idNoClient ID for OAUTH2 authentication on the callback.
auth_token_urlNoToken URL for OAUTH2 authentication on the callback.
flow_directionYesDirection filter: 'In' for incoming flows (from PDP to OD), 'Out' for outgoing flows (from OD to PDP).
signature_algoNoSignature algorithm: RS256, HS256, ECDSA, EDDSA_25519, RSA_PSS, EDDSA_448.
processing_ruleNoOptional processing rule filter: B2B, B2BInt, B2C, B2G, etc.
auth_client_secretNoClient secret for OAUTH2 authentication on the callback.
auth_user_passwordNoPassword for BASIC authentication on the callback URL.
confirmation_tokenNoConfirmation token from a previous call. Omit on the first call; supply on the second call to execute.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so description carries full burden. It discloses the POST behavior to callback URL and the human-in-the-loop requirement. However, it does not mention potential limits (e.g., max webhooks), idempotency, or what happens on duplicate creation, leaving minor gaps.

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?

Three concise paragraphs: purpose, behavior, usage instructions. Each sentence serves a purpose, no redundancy, and critical info is front-loaded (verb + resource).

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

Completeness4/5

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

For a complex tool (14 params, no annotations) with an output schema (unreferenced), the description covers main workflow, filters, and the confirmation mechanism. It lacks mention of response format or error conditions but sufficiently orients an AI agent.

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?

Schema describes all parameters with 100% coverage, so baseline is 3. The description adds value by explaining the callback URL constraints (HTTPS, reachable) and tying filters (flow_type, flow_direction, etc.) together. It also clarifies the confirmation_token usage beyond schema.

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?

The description clearly states 'Subscribe to webhook notifications' with specific context ('Approved Platform'), verb 'subscribe', and resource 'webhook notifications'. It explains the event-triggered POST behavior, distinguishing it from sibling tools like list_webhooks or delete_webhook.

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

Usage Guidelines5/5

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

Provides explicit step-by-step guidance on the human-in-the-loop two-call process: first without confirmation_token to show summary, then with token to execute. This clearly instructs when and how to use the tool, with no ambiguity.

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/cmendezs/mcp-facture-electronique-fr'

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