Skip to main content
Glama
Upload-Post

Upload-Post

Official

Resolve a LinkedIn company Page

resolve_linkedin_organization
Read-only

Resolve a LinkedIn company, showcase or school Page from its URL, vanity name or ID into an exact @mention string, so the Page links correctly in a LinkedIn post.

Instructions

Turn any LinkedIn company, showcase or school Page (its URL, vanity name, numeric id or urn:li:organization:ID) into { urn, id, name, vanity_name, mention }, so it can be @mentioned in a LinkedIn post. LinkedIn only links a company mention when the name matches the Page's name exactly, capitals included; otherwise it is published as plain text. Put the returned mention (@[Exact Name](urn:li:organization:ID)) in the LinkedIn text of upload_text, upload_photos, upload_video or upload_document. Works for any public Page, not only the ones the user administers. People cannot be resolved (400 linkedin_person_not_resolvable): a person can only be mentioned with an urn:li:person id Upload-Post already returned, such as a comment author. Uses the profile's LinkedIn connection; results are cached (cached). Errors: 404 organization_not_found, 403 linkedin_permission_missing (reconnect LinkedIn), 401 linkedin_reauth_required, 429 rate_limited / linkedin_rate_limited.

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": {
      "user": "<user>",
      "url": "<url>"
    },
    "name": "resolve_linkedin_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Page to resolve: linkedin.com/company/<vanity> (or /showcase/, /school/) URL, the vanity name (with or without @), the numeric organization id, or urn:li:organization:ID.
userYesUpload-Post profile name with a connected LinkedIn account.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the readOnly/openWorld annotations by disclosing that it uses the profile's LinkedIn connection, that results are cached, and by enumerating the failure modes (404 organization_not_found, 403 linkedin_permission_missing with the reconnect remedy, 401 reauth, 429 rate limit variants, 400 person_not_resolvable). The exact-name-match requirement that governs whether LinkedIn renders the mention is also surfaced. It does not discuss latency or cache TTL, which keeps it from a 5.

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?

Front-loaded with the core transform before rules, error codes, and the mention format. Dense but nearly every clause carries operational meaning; the trailing error-code list is the one part that reads as reference material rather than guidance, slightly bloating a single unbroken paragraph.

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?

An output schema exists, yet the description still names the returned fields and the exact `mention` syntax, closing the loop from resolution to usage. For a two-parameter read-only lookup with full annotation and schema coverage, nothing an agent needs to invoke it or handle failure is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both params are already documented; the description still adds value by framing the url input as the identity of the Page to resolve and tying the result to the exact-capitalization matching rule. Minor overlap with the schema's own enumeration of accepted url forms keeps it at 4 rather than 5.

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 concrete transform: turn a LinkedIn Page identifier (URL, vanity, numeric id, urn) into `{ urn, id, name, vanity_name, mention }`, with the downstream use (@mention in a post) named immediately. It is unmistakably distinct from the upload_* siblings, which consume the output rather than produce it.

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?

Explicitly scopes applicability ('Works for any public Page, not only the ones the user administers') and states a hard exclusion with the alternative path: people cannot be resolved, a person needs an urn:li:person id previously returned by Upload-Post (e.g. a comment author). It also points to where the result goes (LinkedIn text of upload_text/upload_photos/upload_video/upload_document), so the agent knows the call sequence.

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

Deploy Server

Other Tools