Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn organization jobs

linkedin_live_organization_jobs_v2
Read-onlyIdempotent

List jobs for specified LinkedIn organizations using required organization IDs; use cursor to retrieve additional pages when results are paginated.

Instructions

List jobs for LinkedIn organizations. Requires organizationIds. Returns a list (use cursor when paginated).

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": {
      "organizationIds": "<organizationIds>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_organization_jobs_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
cursorNo
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
organizationIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the return shape ('Returns a list') and a cursor-based pagination hint, which is real added context, but says nothing about rate limits, result caps, or the format of organizationIds.

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?

Three short sentences, front-loaded with purpose and then the required parameter, with zero filler. The parenthetical pagination note is slightly compressed but still readable.

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?

For a read-only list tool with no output schema, the description covers the essential call contract (required param, pagination) but omits how organizationIds should be formatted, whether multiple IDs are supported, and any result-size expectations — gaps that matter for a 6-parameter tool.

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 coverage is 50%, with context, llm_model and conversation_id already documented in-schema and start and cursor undocumented. The description compensates partially by flagging organizationIds as required and explaining that cursor is for pagination, but leaves the type/format of organizationIds and the meaning of 'start' unaddressed.

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?

States a specific verb and resource: 'List jobs for LinkedIn organizations.' An agent can distinguish this from job-search and single-job siblings by the organization scoping, though no sibling is named explicitly.

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?

The description states the prerequisite ('Requires organizationIds') and hints at pagination, but gives no when-to-use vs. when-not guidance and never routes the agent toward linkedin_live_jobs_search_v2 or linkedin_live_job_get_v2 as alternatives.

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