Skip to main content
Glama

get_global_emotes

Retrieve the list of global emotes available on Twitch for use in chat and content creation.

Instructions

グローバルエモートのリストを取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_global_emotes' tool. Fetches global emotes using the Twitch API client and formats the response with emote ID, name, and image URLs at 1x, 2x, and 4x scales.
    export async function handleGetGlobalEmotes(apiClient: ApiClient) {
      const emotes = await apiClient.chat.getGlobalEmotes();
    
      return formatResponse(
        emotes.map(emote => ({
          id: emote.id,
          name: emote.name,
          urls: {
            url1x: emote.getImageUrl(1),
            url2x: emote.getImageUrl(2),
            url4x: emote.getImageUrl(4),
          },
        }))
      );
    }
  • Tool definition including the schema for 'get_global_emotes', which has no required input parameters.
    {
      name: 'get_global_emotes',
      description: 'グローバルエモートのリストを取得します',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:125-126 (registration)
    Registers and dispatches the 'get_global_emotes' tool handler in the MCP CallToolRequestSchema switch statement.
    case 'get_global_emotes':
      return await handleGetGlobalEmotes(this.apiClient);
  • src/index.ts:77-79 (registration)
    Registers the tool list including 'get_global_emotes' via toolDefinitions for ListToolsRequestSchema.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: toolDefinitions,
    }));
  • src/index.ts:19-19 (registration)
    Imports the handler function for 'get_global_emotes'.
    import { handleGetGlobalEmotes, handleGetGlobalBadges } from './tools/handlers/chat.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('get a list') without any additional context on traits like rate limits, authentication needs, pagination, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, clear sentence in Japanese that directly states the tool's purpose without any fluff or redundancy. It is appropriately sized and front-loaded, making it efficient and easy to understand, with every word earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the basic action but lacks completeness for effective use, as it does not cover behavioral aspects like response format or platform context. With no output schema, the agent is left guessing about return values, making this description incomplete for optimal tool invocation.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there is no need for parameter details in the description. The baseline for 0 parameters is 4, as the description does not need to compensate for any missing schema information, and it correctly avoids unnecessary parameter discussion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'グローバルエモートのリストを取得します' translates to 'Get a list of global emotes.' This specifies the verb ('get') and resource ('global emotes list'), making the intent unambiguous. However, it does not differentiate from sibling tools like 'get_global_badges' or 'get_channel_info,' which also fetch lists, so it misses full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, such as whether it's for Twitch or another platform, or how it differs from similar tools like 'get_global_badges.' This lack of usage context leaves the agent without direction on selection.

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/mtane0412/twitch-mcp-server'

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