Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_reaction

Add an emoji reaction to a Google Chat message using a Unicode emoji character. The reaction is visible to all space members.

Instructions

Add an emoji reaction to a Chat message.

Side effects: creates a reaction visible to everyone in the space. Custom Workspace emoji are not supported here (Unicode only). For posting a new message use send_message. Requires the chat_write OAuth scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_google_email": "<user_google_email>",
      "message_id": "<message_id>",
      "emoji_unicode": "<emoji_unicode>"
    },
    "name": "create_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
message_idYesMessage resource name ("spaces/<space>/messages/<msg>") from get_messages or search_messages.
emoji_unicodeYesSingle Unicode emoji character, e.g. "👍" (thumbs up) or a literal emoji like a smiley.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / emoji_unicode / description
      Previous value: -"The emoji character to react with (e.g. 👍)."New value: +"Single Unicode emoji character, e.g. \"👍\"\n(thumbs up) or a literal emoji like a smiley."
    • changedInput schema / properties / message_id / description
      Previous value: -"The message resource name (e.g. spaces/X/messages/Y)."New value: +"Message resource name\n(\"spaces/<space>/messages/<msg>\") from get_messages or\nsearch_messages."
    • addedInput schema / properties / user_google_email / description
      Added value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses side effects ('creates a reaction visible to everyone'), limitations (Unicode only), and auth requirements. Could be more detailed about idempotency or response, but covers key behavioral aspects.

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 description is four sentences, each serving a purpose: action, side effects, limitations/alternative, auth. No redundant information, efficiently front-loaded.

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?

Given no annotations, the description covers purpose, usage guidelines, side effects, and limitations. An output schema exists, so return value details are not needed. The description is thorough enough for a typical create tool.

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 coverage is 100%, but the description adds value by clarifying that 'emoji_unicode' must be a Unicode character and that custom emoji are not supported. This extra context helps the agent avoid invalid 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 'Add an emoji reaction to a Chat message' with a specific verb and resource. It distinguishes from sibling tools like 'send_message' by noting that it is for reactions, not posting new messages.

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?

The description explicitly says when not to use it (Custom Workspace emoji not supported), provides an alternative ('For posting a new message use send_message'), and specifies the required OAuth scope ('Requires the chat_write OAuth scope').

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