callable
Server Details
API for AI agents to delegate tasks to real humans.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 3 of 3 tools scored.
Each tool has a clear, distinct purpose: submit_task initiates a task, get_task_status polls for results, and review_task handles approval or dispute. There is no functional overlap.
All tool names follow a consistent verb_noun pattern (submit_task, get_task_status, review_task) using snake_case, making them predictable and easy to understand.
Three tools is the minimal set needed for a complete task lifecycle (submit, poll, review). Adding more would likely introduce redundancy.
The tools cover the core workflow of submission, status polling, and review. A missing cancel or delete operation is a minor gap, but auto-approval mitigates it.
Available Tools
3 toolsget_task_statusRead-onlyIdempotentInspect
Poll the status and retrieve the result of a previously submitted task. Returns the current status (pending, in_progress, pending_review, completed, disputed), the result payload, and any output URLs (video, screenshot). Use this in a polling loop after submit_task if no callback_url was provided.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task ID returned when the task was submitted |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | No | Task result payload when completed |
| status | Yes | |
| task_id | Yes | |
| operator | No | Name of the operator who completed the task |
| output_url | No | URL to download output file (video, screenshot, etc.) |
| completed_at | No | ISO timestamp of completion |
review_taskIdempotentInspect
Optional. Approve or dispute a task that is in pending_review status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task ID returned by submit_task. | |
| decision | Yes | approve to accept the result and release payment; dispute to reject it and request a resubmission. | |
| dispute_reason | No | Required when decision = 'dispute'. What went wrong with the submission. | |
| what_is_needed | No | Required when decision = 'dispute'. What the operator must do for the submission to be accepted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| status | Yes | |
| success | Yes |
submit_taskInspect
Submit an account verification task to a real human operator. Use this when your agent is blocked on something only a real person can complete — a KYC check, a platform sign-in or 2FA prompt, a CAPTCHA, an identity confirmation, or any verification step that requires a human. The task is charged automatically via Stripe ($39). A vetted operator claims it, performs the verification on real hardware, and returns the result (with optional screenshot) to your callback_url or via get_task_status. Typical completion: 30 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| task_type | Yes | account_verification — a real human verifies an account, KYC check, sign-in, or CAPTCHA on real hardware and returns structured proof ($39). | |
| callback_url | No | Webhook URL to receive a POST request with the task result when completed. Recommended for async agent workflows. If omitted, poll get_task_status instead. | |
| instructions | Yes | Structured input for account_verification. Required fields: platform (e.g. 'gmail', 'stripe'), url (where to perform the verification), credentials (login info or how to obtain the code), what_to_verify (what the operator must confirm). Optional: screenshot_required (boolean, default true), additional_notes. | |
| deadline_minutes | Yes | Time in minutes the operator has to complete the verification after claiming it. Minimum 20. Recommended: 30. | |
| payment_credential | No | Stripe Link Agent Wallet Single-use Payment Token (SPT) for fully autonomous agent payments with no human intervention required. Omit if the developer account has a saved card on file. |
Output Schema
| Name | Required | Description |
|---|---|---|
| status | Yes | Current task status |
| message | No | Confirmation or error message |
| task_id | Yes | Unique identifier for the submitted task |
| estimated_completion | No | Estimated completion time based on deadline_minutes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!