Skip to main content
Glama

List Profiles

list_profiles
Read-onlyIdempotent

[Read · free] List all tracked LinkedIn profiles for the authenticated user. Returns profile IDs needed by other tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two things beyond them: the "[Read · free]" marker (no credit spend, relevant given siblings like get_cost_estimate and get_credit_balance) and the per-authenticated-user scoping. It doesn't touch ordering or whether untracked profiles appear, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero waste, with the access/cost tag and the core purpose front-loaded. Nothing here could be cut without losing routing information.

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

Completeness4/5

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

A zero-parameter, read-only list tool with no output schema is fully covered by naming what is returned (profile IDs), and the [Read · free] tag covers the cost question. The only residual gap is what other fields each profile entry carries, which the description leaves unstated.

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?

Zero-parameter tool, so there is no parameter semantics to explain and the baseline applies. The description correctly doesn't invent inputs, and the empty input schema is consistent with the "list all" framing.

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?

Specific verb+resource ("List all tracked LinkedIn profiles") with a clear scope: the authenticated user's own tracked profiles, which separates it from the network-wide helpers like get_post_engagers_by_company. The second sentence adds the output essence (profile IDs), so an agent knows this is the ID-discovery entry point rather than a profile-detail tool such as get_profile_summary.

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?

"Returns profile IDs needed by other tools" tells the agent when this tool is the right prerequisite step, which is real routing guidance. It stops short of naming a specific alternative or stating when-not to call it (e.g., if you already have an ID), so it is clear context without explicit exclusions.

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.

Resources