Skip to main content
Glama

Connect LinkedIn

flypost_connect_linkedin

Start connecting LinkedIn for publishing: returns an OAuth URL the USER must open in a browser to authorise. Never open or complete it yourself. Afterwards, check with flypost_get_linkedin_connection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flypost_connect_linkedin"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, open-world, non-destructive call. The description goes well beyond that by disclosing the return value type (OAuth URL), the required human-in-the-loop step in a browser, and the follow-up verification tool. These are exactly the operational facts an agent cannot infer from annotations.

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?

Three short sentences, front-loaded with the action and its output, then the constraint, then the follow-up. No redundant restatement of the tool name or title.

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

Completeness5/5

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

For a one-optional-param initiation tool with no output schema, the description supplies the missing return-value information and the post-call verification path. Nothing needed to invoke or sequence it correctly is absent.

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?

The single parameter's meaning is fully documented in the schema ('Project id; omit for the active project.'), and the description adds nothing about it. With 100% schema coverage the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Start connecting LinkedIn for publishing') and immediately specifies what the call yields: an OAuth URL. It also implicitly separates itself from the sibling 'flypost_get_linkedin_connection', which is named later as the follow-up rather than the initiation step.

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?

Gives explicit when-to-use (starting the LinkedIn connection), an explicit prohibition ('Never open or complete it yourself'), and names the correct next tool to call afterwards. The division of labour between agent and USER is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.