Skip to main content
Glama

LinkedIn: Submit company member OTP

linkedin_submit_company_member_otp
Destructive

Complete LinkedIn company-member verification. Reuse the same email and exact challenge_id returned by linkedin_verify_company_member_email, and submit only the real user-provided code; never invent or loop over codes.

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": {
      "company_id": "<company_id>",
      "product": "<product>",
      "email": "<email>",
      "challenge_id": "<challenge_id>",
      "code": "<code>"
    },
    "name": "linkedin_submit_company_member_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesActual verification code received by the user. Never invent.
emailYes
productYesclassic
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
company_idYesExact LinkedIn company ID from company search/profile resolution; never use company name or slug unless a resolver explicitly converts it.
challenge_idYesExact challenge_id returned by linkedin_verify_company_member_email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is already visible. The description adds genuinely non-obvious behavioral constraints beyond that: codes are one-time and user-supplied, and the agent must never invent or loop over codes — implicitly warning that repeated wrong submissions are harmful. It does not spell out the actual consequence of failure (lockout, challenge invalidation) or return behavior.

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 tightly packed sentences with zero filler. The action is front-loaded and the prerequisite plus the anti-hallucination guard follow in the same breath.

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

Completeness3/5

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

This is a mutating, non-idempotent step in a multi-step verification flow with five required parameters and no output schema, so the description is reasonable but not full. It covers the prerequisite chain and the code constraint, but says nothing about what a successful or failed submission returns (verification status, error cases), which matters precisely because there is no output schema to fall back on.

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 a moderate 67%, and the schema itself already documents code, email, company_id, challenge_id and account_id well. The description's added value is the cross-call coupling — the email and challenge_id must match the prior verification call — which the schema does not express. Beyond that it adds no format or constraint detail the schema lacks.

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 ('Complete LinkedIn company-member verification') and immediately clarifies the actual payload action ('submit... the real user-provided code'). It also distinguishes itself from the closely related sibling linkedin_verify_company_member_email by positioning that tool as the source of the challenge, so an agent can tell the two apart without opening either 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?

Explicitly establishes the prerequisite sequence: this tool is used after linkedin_verify_company_member_email and must reuse the same email and exact challenge_id from that call. That is clear when-to-use guidance. It stops short of stating when not to call it (e.g., expired challenge, exhausted attempts) or what alternative to use if the challenge is stale.

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.