Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: Connect an account with an `li_at` session cookie the member took from their own browser. A cookie is a credential: do not ask for one in a conversation — POST /linkedin/connect/link {action: connect} is the way to offer this to a person. Forwarded once, never stored.

complete_connect_cookie
Destructive

Connect an account with an li_at session cookie the member took from their own browser. A cookie is a credential: do not ask for one in a conversation — POST /linkedin/connect/link {action: connect} is the way to offer this to a person. Forwarded once, never stored. -- MakeHybrid API plan, POST /linkedin/connect/cookie, group 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": "complete_connect_cookie"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body for POST /linkedin/connect/cookie.
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this as a destructive, non-idempotent, open-world write operation. The description adds important credential-handling context beyond annotations: the cookie is sensitive, it is forwarded once and never stored, and it should not be solicited in conversation.

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?

The useful security warning and alternative are front-loaded before the API metadata. It is a bit redundant because the description repeats the title, and the trailing API plan/endpoint line is less important, but overall it is tightly scoped.

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 destructive credential-submission tool with no output schema, the description gives adequate safety and usage context, including the recommended alternative flow. It could be more complete by specifying the expected request body field for the cookie and any consequences of a failed or revoked credential.

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 the schema already describes the generic `body` and `query` parameters. The description mentions the `li_at` cookie but does not clarify payload shape or where the cookie value should be supplied, so it does not add much beyond the schema baseline.

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: connect an account using an `li_at` session cookie taken from the member's own browser. It also distinguishes this tool from the sibling `complete_connect_link` by naming the safer alternative for offering connection in conversation.

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?

It explicitly says not to ask for a cookie in a conversation and directs the agent to `POST /linkedin/connect/link {action: connect}` as the way to offer this to a person. That is direct when-to-use and when-not-to-use guidance tied to a specific sibling.

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

All mcp toolsInspect
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