Skip to main content
Glama
karbassi

slack-mcp

by karbassi

conversations_request_shared_invite_list

List shared channel invite requests with optional filters for approval status, user, and pagination.

Instructions

List shared channel invite requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from ``response_metadata.next_cursor`` in a prior response.
include_approvedNoInclude already-approved requests in the results.
include_deniedNoInclude denied requests in the results.
include_expiredNoInclude expired requests in the results.
invite_idsNoRestrict results to these specific invite request IDs.
limitNoMaximum number of requests to return per page.
user_idNoOnly return requests made by this user ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. Description does not disclose any behavioral traits (e.g., permissions, rate limits, return format). Minimal beyond the action 'list'.

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?

Single sentence, no superfluous words. Efficiently conveys the tool's purpose.

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 7 optional parameters with schema descriptions and an output schema, the description is concise but sufficient. Could optionally mention pagination or outcomes, but minimal.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for each parameter. Description adds no additional semantic value beyond what schema provides, meeting baseline.

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?

Description clearly states 'List shared channel invite requests.' Verb (list) + resource (shared channel invite requests) is specific and distinguishes from siblings like approve/deny/accept.

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?

No guidance on when to use this tool vs alternatives. With many shared invite siblings, explicit usage context is missing.

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/karbassi/slack-mcp'

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