Skip to main content
Glama

SiteSpeak Chatbot Manager

by ai.sitespeak.api

Add Suggested Message Tool

add_suggested_message

Add a suggested message (a clickable prompt shown to visitors). For type "ai" (default) provide a prompt - the message sent when clicked. For redirect/email types provide an action (a URL or email address).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe button label shown to visitors (max 100), e.g. "Pricing Plans".
typeNoai (default), redirect, email, intercom, follow_up, follow_up_link, follow_up_email, escalate.
actionNoA URL or email (max 200). Required for type redirect, email, follow_up_link, follow_up_email.
promptNoThe message sent when clicked (max 200). Required for type ai and follow_up.
chatbot_idYesThe chatbot id.

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Explains behavior per type (sending message vs redirect) but does not disclose permissions, idempotency, or limits.

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?

Extremely concise: two sentences, front-loaded with purpose. Every sentence adds value.

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?

Adequate for a creation tool with 5 parameters and no output schema. Missing details on return value or duplicate handling, but sufficient for typical use.

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?

100% schema description coverage gives baseline 3. Description adds meaning by linking prompt and action to the type (e.g., 'prompt required for ai and follow_up'), which is not fully explicit in 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?

Clear verb+resource: 'Add a suggested message (a clickable prompt shown to visitors).' Distinguishes from sibling tools like list_suggested_messages and update_suggested_message.

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?

Explicit guidance per type: 'For type 'ai' (default) provide a prompt... For redirect/email types provide an action...' Clear context but no explicit when-not-to-use or alternatives.

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

All SiteSpeak Chatbot Manager 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.8/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (sources, suggested messages, chatbots, inbox, leads, analytics, insights). There is no ambiguity between tool purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (add_, get_, list_, recrawl_, update_). The naming convention is uniform and predictable.

Tool Count5/5

15 tools is well-scoped for a chatbot manager. The set covers all key functional areas without being excessive or insufficient.

Completeness3/5

The tool surface is largely complete but lacks delete operations: there is no 'remove_suggested_message' (though referenced in a description) and no way to delete a source. These are notable gaps.

Resources