Share by DeltaBreen

post_request_link

Post a file request's link into a connected Slack bot channel so a person can upload a file or answer the form there. Set to to a person's email to DM them (e.g. ask a colleague for a secret) or channel for a channel. Create the page first, pick a channel from list_channels. The service builds the link from the page id — you cannot post any other URL, and the link never carries a file key. A private page also posts a fresh access code beside the link, so the recipient needs nothing handed to them separately.

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": {
      "request_page_id": "<request_page_id>",
      "channel_id": "<channel_id>"
    },
    "name": "post_request_link"
  }
}

Input Schema

Name	Required	Description
`to`	No	Slack-bot channel only: the person to DM, by email. Resolved to their Slack user.
`channel`	No	Slack-bot channel only: a channel name/id to post to instead of a person.
`message`	No	A short note shown above the link in the channel.
`channel_id`	Yes	The id of a channel from list_channels.
`request_page_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses key behavior: the service builds the link from the page id, arbitrary URLs cannot be posted, the link never contains a file key, and private pages post a fresh access code beside the link. These are meaningful constraints and side effects that help the agent call the tool correctly.

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 front-loaded with the purpose, then moves efficiently through targeting, prerequisites, URL constraints, and private-page behavior. Every sentence adds useful context and there is no obvious waste.

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?

With annotations covering safety and open-world behavior, the description supplies the important operational and side-effect context for a Slack posting tool. It is slightly incomplete around the required `channel_id` when using `to` or `channel`, but overall it gives enough to call the tool correctly.

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 high, but the description adds useful meaning for `to` and `channel` targeting and clarifies that `request_page_id` is used by the service to build the posted link. It does not explain the required `channel_id` versus optional `channel` relationship or mention `message`, leaving some parameter nuance to the 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?

The description states a specific verb and resource: posting a file request's link into a connected Slack bot channel so someone can upload or answer there. It distinguishes the action from siblings by focusing on Slack delivery and the DM/channel targeting, so an agent can identify the tool without opening the schema.

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?

It gives clear operational guidance: create the page first, pick a channel from list_channels, and use `to` for a DM or `channel` for a channel. It does not explicitly compare this tool to alternatives like send_request or send_share_link, so it stops short of full when-not-to-use guidance.

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

All Share by DeltaBreen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?