Skip to main content
Glama

Add LinkedIn profiles during setup

flypost_add_onboarding_linkedin

Give Flypost the user's LinkedIn profile so it can learn how they write from their public posts. Pass an empty list to skip.

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": {
      "profile_urls": "<profile_urls>"
    },
    "name": "flypost_add_onboarding_linkedin"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project, or the only project if there is just one.
profile_urlsYesUp to 3 linkedin.com/in/ profile URLs. Empty to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (non-read-only, open-world, non-destructive), so the bar is lower. The description does add useful context about why the data is collected and what it is derived from (public posts), but it omits what happens on a bad or private URL, whether the profiles are stored permanently, and any rate/verification behavior.

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 short sentences with the purpose front-loaded and the opt-out second; nothing is wasted. It is slightly under-specified rather than over-long, and the skip instruction could be tightened to match the schema wording.

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 two-parameter onboarding slice with full schema coverage and no output schema, the description covers purpose and the skip path adequately. The missing piece is its relationship to the other onboarding tools and what the collected profiles affect downstream.

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 description coverage is 100%, so both parameters are already documented in the schema, including the max of 3 and the linkedin.com/in/ format. The description only restates the empty-list skip semantics, adding no extra meaning beyond the schema; baseline 3 applies.

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?

The description names a specific verb and resource (give Flypost the user's LinkedIn profile) and states the payoff (learning how they write from public posts). It does not explicitly contrast itself with the similarly named flypost_connect_linkedin sibling, so an agent must infer that this is the onboarding-step variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Pass an empty list to skip" gives a clear opt-out condition, which is genuine when-not guidance for this onboarding step. However, it never says when to prefer this over flypost_connect_linkedin or how it sequences with the other onboarding tools, leaving the alternative routing implied.

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.