Skip to main content
Glama
Sign In
Appmixer MCP

Appmixer MCP

by Appmixer-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Trigger URL

get_trigger_url
Read-only

Retrieve the public webhook URL for a flow's trigger component so another flow can POST to it and chain automations; the flow must be running to accept requests.

Instructions

Get the public webhook URL of a trigger component (e.g. WebhookTrigger) in one of your flows. Use it to chain flows: another flow POSTs to this URL via appmixer.utils.http.Post — no credentials needed, the endpoint is public. The flow must be running for the webhook to actually accept requests.

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe ID of the flow the trigger belongs to.
component_idYesThe ID of the trigger component.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the simple read-only hint, the description discloses vital behavioral traits including that the endpoint requires no credentials, is publicly accessible, and requires the source flow to be actively running. This rich operational context is extremely helpful.

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?

The definition is maximally efficient. It moves from the core function to the method of use, then to critical constraints, ensuring that all necessary decision-making context is provided without unnecessary jargon or repetition.

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 the lack of an output schema, the description is perfectly complete. It not only delivers the URL but also explains exactly how that URL should be used and under what conditions it will work, eliminating practical ambiguity for the 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?

With 100% schema coverage, the parameters are clear. The description adds value by contextually linking the IDs to their roles within the flow hierarchy (trigger component in a flow), which is helpful for conceptual understanding of the inputs.

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 the purpose: to get the public webhook URL of a specific trigger component. It provides a concrete example (e.g., WebhookTrigger) which further refines the resource and distinguishes it from general component metadata retrieval tasks.

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?

It provides explicit instructions on usage, detailing that the URL should be used for chaining flows via a POST request. Crucially, it defines the operational requirements, such as the flow needing to be running for the webhook to be functional.

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