Skip to main content
Glama
Sign In
recruiting-ops-mcp

recruiting-ops-mcp

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

slack_conversations_invite

Invite up to 1,000 Slack users to a channel; set force to continue past invalid IDs and return which invites succeeded.

Instructions

Add people to a channel. With force set, Slack adds everyone it can and reports the rest alongside a success, so read the result.

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": {
      "channel": "<channel>",
      "users": "<users>"
    },
    "name": "slack_conversations_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoInvite everyone who can be invited rather than failing the whole call on the first bad id.
usersYesComma-separated user IDs, up to a thousand.
channelYesThe channel to invite people to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true), and the description adds real behavioral context beyond them: with force set, Slack invites everyone it can and reports the failures alongside a success rather than failing outright. That partial-success semantics is the kind of detail annotations cannot express. It stops short of 5 because permission requirements and rate-limit/error behavior are unstated.

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?

Two sentences, zero padding, with the core action front-loaded and the force caveat second. Efficient, though the second sentence is dense and could be split for scanability.

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?

For a mutation tool with no output schema, the description correctly warns that partial failures are reported in the response and tells the agent to inspect the result. Annotations carry the safety profile. The main gap is that it never states permission requirements or what a failure response looks like.

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%, so all three parameters (channel, users, force) are already documented in the schema. The description restates the force behavior and adds the nuance that partial results are reported 'alongside a success,' which slightly enriches the schema's wording but does not cover anything the schema omits. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Add people to a channel'), which is unambiguous and distinct from sibling slack_chat_post_message. However, it does not name or contrast any alternative tool, so it stops short of full sibling differentiation.

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?

There is no explicit guidance on when to use this versus alternatives, nor any prerequisites (e.g. bot must be in the channel, needs channel-management scope). The only usage-adjacent statement is 'read the result,' which is a hint, not routing guidance.

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