Skip to main content
Glama
Sign In

Linked API

by io.github.Linked-API
OverviewDiscussionsAdmin

get_changelog

Read-only

Read the public Linked API changelog: what was released and when, newest first. Use it when the user asks what is new or recently changed in Linked API, or whether Linked API supports something yet — a capability may have shipped recently, so check here before saying it does not exist. Each release has a date and items with a title, a body and docs, a path on https://linkedapi.io (prefix it to link the user to the documentation). Needs no Linked API tokens and does not start a LinkedIn workflow. The same changelog is published at https://linkedapi.io/changelog.

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": "get_changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly return releases for the week containing this point and later: an ISO 8601 date (e.g. '2026-10-01') or an instant with a time zone (e.g. '2026-10-01T00:00:00Z'). A release covers a week and is dated by its first day, so one dated a few days before since can still be included. Omit to get the whole changelog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond readOnlyHint/openWorldHint: no tokens required, no LinkedIn workflow is started, releases are grouped by week with date/title/body/docs fields, and docs paths are relative to linkedapi.io. The mirror URL confirms it is a public, network-facing read.

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 trigger conditions, then behavioral constraints and return shape. It is dense but every sentence carries information; the closing URL sentence is mildly redundant with the docs-path guidance but still useful for discovery.

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?

With one optional parameter and no output schema, the description supplies exactly what is missing: the per-release field structure (date, title, body, docs), the path prefixing rule, and the auth/workflow side effects. An agent can call this and render results correctly without further inference.

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 100% and the 'since' definition already explains ISO 8601 formats, the week-granularity edge case, and the omit-to-get-everything default. The prose adds no additional parameter meaning beyond the schema, so baseline 3 applies.

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 ('Read the public Linked API changelog') plus ordering ('newest first') and content ('what was released and when'). It is unmistakably distinct from every sibling, which are LinkedIn workflow operations.

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?

Gives concrete triggers ('asks what is new or recently changed', 'whether Linked API supports something yet') and an explicit negative guardrail: check here before claiming a capability does not exist. No alternative tool competes for this task, and the description makes that clear implicitly by scoping it to API metadata rather than user data.

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

All Linked API 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