Skip to main content
Glama

Read people to exclude from a file

parse_exclusions_file

«Исключить уже знакомых»: a CSV, TSV, TXT or XLSX file with the people the user already knows (LinkedIn links in any column) -> the profile links found (pass them as exclude_urls of create_search) and the company pages (exclude_company_urls). Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/exclusions]

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": {
      "file_name": "<file_name>",
      "data_base64": "<data_base64>"
    },
    "name": "parse_exclusions_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameYesThe file's name with its extension.
data_base64YesThe file's bytes, base64.
onboarding_idNoThe onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the same new search.

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?

Beyond the annotations, the description discloses important side effects and constraints: the first onboarding assistant call spends one brief, a free account has one search brief and may call each assistant once, and the tool returns an onboarding_id that must be threaded into subsequent calls. These details are essential for correct invocation and are not inferable from the annotations alone.

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?

The description is front-loaded with the purpose and then explains onboarding constraints and return usage. It is dense and includes a Russian UI phrase, but no sentence is clearly wasted; the REST endpoint note is the only marginally redundant item.

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?

There is no output schema, so the description must explain return values and downstream usage. It does so by naming the returned profile links, company pages, and onboarding_id, and by explaining how to pass them to create_search and later assistant calls. For a stateful onboarding helper, this is complete enough to call correctly.

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 schema already documents each parameter. The description still adds useful meaning by specifying accepted file formats, indicating that LinkedIn links may appear in any column, and explaining how the parsed results map to create_search parameters.

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 states a specific action and resource: it parses a CSV, TSV, TXT or XLSX file of people the user already knows and returns LinkedIn profile links and company pages. It clearly distinguishes its output from create_search by saying those links should be passed as exclude_urls/exclude_company_urls.

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?

It gives clear usage context: this is part of a new search's onboarding, it is the first assistant call, and the returned onboarding_id must be passed to later assistant calls and create_search. It does not explicitly state when not to use it, but the onboarding context is strong enough to guide selection.

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