Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Look Up LinkedIn Company Page

resolve_linkedin_organization
Read-onlyIdempotent

Resolve a LinkedIn company page URL or exact vanity name into organization details and a ready-to-paste mention for tagging it in posts.

Instructions

Look up a LinkedIn company page so a LinkedIn post can mention (tag) it. Takes the page URL (https://www.linkedin.com/company/acme/), its vanity name (acme, the part after linkedin.com/company/) or @acme. LinkedIn only matches the exact vanity name, so this is not a search: 'acm' or a company name with spaces finds nothing, and you should ask the user for the page URL when you do not know the vanity name. Returns { organization } with id, name, vanityName, urn and mention. Paste mention as it is into the LinkedIn text of create_post, update_post or bulk_schedule_posts; when the post also goes to other platforms, put it in platformTexts for LINKEDIN, because other platforms show the mention syntax as raw text. Fails with linkedin_organization_not_found (404) when no page has that vanity name, linkedin_organization_query_invalid (400) when the query is neither a page URL nor a vanity name, and linkedin_organization_lookup_unavailable (400) when no LinkedIn account of the workspace could run the lookup: tell the user to connect or reconnect a LinkedIn account in AdaptlyPost, ideally a company page they administer. Nothing is posted.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe company page URL, its vanity name, or @vanity, e.g. "https://www.linkedin.com/company/acme/" or "acme"
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with organization: { id, name, vanityName, urn, mention }. Paste mention into the LinkedIn post text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description still adds the error taxonomy with status codes (linkedin_organization_not_found 404, linkedin_organization_query_invalid 400, linkedin_organization_lookup_unavailable 400) and the remediation ('connect or reconnect a LinkedIn account... ideally a company page they administer'). The closing 'Nothing is posted' explicitly reinforces that no side effect occurs.

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 purpose, then constraint, then return shape, then error handling – a sensible order with no filler sentences. It runs long as one unsegmented paragraph, which slightly hurts scanability for a definition carrying this much conditional detail.

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?

For a read-only lookup with two parameters, it covers input forms, exact-match semantics, the returned fields, downstream usage of the result, and all failure modes. Although an output schema exists (so return-value documentation was optional), the explicit mention of 'mention' usage in sibling post tools adds real operational value.

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 the baseline is 3, but the description adds real meaning beyond the schema: it clarifies that only an exact vanity name matches, lists the three accepted input forms with a worked URL example, and ties each malformed input to a specific error code. The workspaceId parameter is left to the schema, which is acceptable given full coverage.

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 opens with a specific verb and resource ('Look up a LinkedIn company page') and immediately states the downstream purpose ('so a LinkedIn post can mention (tag) it'). It also rules out the tempting misreading by declaring 'this is not a search', which separates it from any discovery-style sibling.

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 gives the exact trigger conditions (you need a mention string for create_post, update_post or bulk_schedule_posts), the exclusion ('not a search', so 'acm' or a spaced company name finds nothing), and a concrete fallback ('ask the user for the page URL') when the vanity name is unknown. It even names the downstream parameter to paste into (mention, or platformTexts for LINKEDIN).

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