Skip to main content
Glama

LinkedIn connection status

flypost_get_linkedin_connection
Read-only

Read the project's LinkedIn publishing connection: which identities (the user's profile, company pages, teammates) it can post as. If none is connected, flypost_connect_linkedin gives the user a link to connect.

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_get_linkedin_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The read-only annotation is consistent with 'Read...' and the description adds useful behavior beyond annotations: it explains what the connection status represents and what to do when none is connected. It does not detail auth requirements or exact response fields, but for a simple read with no output schema the return content is described adequately.

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?

Two sentences, front-loaded with the action and followed by the one condition that changes the next step. There is no redundant wording or restatement of schema details.

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?

The tool is a simple read with annotation coverage and no output schema; the description explains the status content and the no-connection path. It could be slightly richer about the response shape or authentication context, but nothing essential for correct invocation is missing.

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 sole project_id parameter is fully documented in the schema, including its default to the active project. The description refers to 'the project's' connection but adds no new syntax, constraints, or semantics beyond the schema, so the baseline score of 3 applies.

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 ('Read the project's LinkedIn publishing connection') and clarifies the relevant content: posting identities such as the user's profile, company pages, and teammates. It also distinguishes the tool from flypost_connect_linkedin by assigning the connect flow to the no-connection case.

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 a clear conditional alternative: when no LinkedIn connection exists, use flypost_connect_linkedin to get a connection link. It does not state a broader when-to-use trigger, such as checking before scheduling a post, but the key handoff and context are covered.

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.