Skip to main content
Glama

send_webex_adaptive_card

Send rich interactive Adaptive Card messages to Webex rooms or individuals. Requires card_body and fallback_text for non-supporting clients.

Instructions

Send an Adaptive Card message to a Webex room or person.

Adaptive Cards are rich, interactive message attachments. Clients that do not support cards will display fallback_text instead.

IMPORTANT — Webhook limitation: Card action submissions (Action.Submit) are delivered to the bot only if a webhook is registered for the "attachmentActions" resource on the Webex platform. Without that webhook, submissions are silently dropped and the bot never receives them. Inform the user of this limitation whenever the card includes interactive actions. To receive submissions, a webhook must be created at developer.webex.com or via the Webex Webhooks API targeting the bot's public HTTPS endpoint.

Args: room_id: Room ID to send the card to (use this OR to_person_id/to_person_email) to_person_id: Person ID to send a direct card to to_person_email: Person email to send a direct card to card_body: List of Adaptive Card body elements (required, non-empty). Each element must have a "type" field (e.g. "TextBlock", "Image", "ColumnSet"). Use build_webex_adaptive_card to generate this from high-level inputs. fallback_text: Plain-text fallback shown to clients that do not support cards (required) card_actions: Optional list of action objects (Action.OpenUrl, Action.Submit, etc.) card_version: Adaptive Card schema version — one of "1.0", "1.1", "1.2", "1.3" (default "1.3") parent_id: Parent message ID for threaded replies

Returns: Standardized response dictionary with success/error information

Examples: result = send_webex_adaptive_card( room_id="Y2lzY29zcGFyazovL3VzL1JPT00v...", fallback_text="Build passed", card_body=[ {"type": "TextBlock", "text": "Build Passed", "weight": "Bolder", "size": "Medium"}, {"type": "TextBlock", "text": "All 42 tests green", "color": "Good"}, ], card_actions=[ {"type": "Action.OpenUrl", "title": "View Logs", "url": "https://ci.example.com"} ], )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
room_idNo
card_bodyNo
parent_idNo
card_actionsNo
card_versionNo1.3
to_person_idNo
fallback_textNo
to_person_emailNo
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that clients without card support will show fallback_text, and warns about silent dropping of Action.Submit submissions if a webhook is missing. It does not cover rate limits, permissions, or side effects, but the key behavioral traits are addressed.

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

Conciseness4/5

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

The description is well-structured with sections (IMPORTANT, Args, Returns, Examples) and front-loaded with the purpose. It is slightly lengthy but every sentence adds value, and the format aids readability. A minor reduction in redundancy could improve conciseness.

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?

The description covers the card structure, fallback, actions, and version, and provides examples. It does not detail error responses or output format beyond 'standardized response dictionary,' but given the tool's complexity and lack of output schema, it is adequately complete. A note on success/error details would enhance completeness.

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

Parameters5/5

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

The description's Args section adds crucial meaning beyond the input schema (which has 0% coverage). It explains mutual exclusivity of room_id/to_person_id/to_person_email, the required nature of card_body and fallback_text, the requirement for a 'type' field in card_body elements, and the purpose of optional parameters. This fully compensates for the schema's lack of descriptions.

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 'Send an Adaptive Card message to a Webex room or person,' specifying the verb (send), resource (Adaptive Card message), and target (room or person). This distinguishes it from sibling tools like send_webex_message (plain text) and send_webex_space_adaptive_card (space-only).

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?

The description explains when to use this tool (sending adaptive cards) and includes a critical limitation about webhook registration for Action.Submit. However, it does not explicitly contrast with other message-sending tools or provide clear when-not-to-use guidance, leaving room for improvement.

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/WebexCommunity/webex-bot-mcp'

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