Skip to main content
Glama

SourceGeek

Get newsletters a person follows

employee_profile_newsletter_interests
Read-only

List the newsletters a person subscribes to (id, name, url, description, frequency, publisher). Paged via page (50 per page).

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": {
      "usernameOrUrl": "<usernameOrUrl>"
    },
    "name": "employee_profile_newsletter_interests"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the returned fields, which matters since there is no output schema, but its 'paged via page (50 per page)' claim is inconsistent with the schema's limit parameter (1-100, default 10) and with the note that results beyond the provider page are not fetched.

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?

Two short sentences, front-loaded with the purpose and followed by the return shape and paging hint; nothing is padded. The only cost is the '50 per page' clause, which is a confusing detail given the limit parameter.

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?

For a read-only list endpoint with fully documented parameters, the description covers purpose, returned fields and pagination, which is nearly enough. The one gap is that the stated page size does not reconcile with the limit parameter or the provider-page caveat in the schema.

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 description coverage is 100%, so page, limit and usernameOrUrl are already documented; the description adds nothing about username-vs-URL handling or return-count semantics. Its '50 per page' assertion actually conflicts with the limit parameter's documented range and default, adding confusion rather than meaning.

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 the newsletters a person subscribes to') and enumerates the returned fields, so the agent knows exactly what it gets back. It does not explicitly name the sibling interest tools (company/group/school/top-voice) that an agent might confuse it with, so differentiation is only implied by the resource noun.

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 implies usage (fetch a person's newsletter subscriptions for a given profile) but gives no explicit when-to-use, when-not-to-use, or prerequisite information. There is no pointer to the sibling interest endpoints for an agent choosing among profile-interest tools.

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