Skip to main content
Glama

SourceGeek

Search posts

employee_search_posts
Read-only

Search public posts by keyword with optional filters: sort (relevance or date_posted), date window (e.g. 'past-24h', 'past-week', 'past-month'), author title, author company ids, author industry ids, from-member usernames, from-company ids, mentions. Returns post text, author, engagement counts, urn/url; paged.

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": {
      "keyword": "<keyword>"
    },
    "name": "employee_search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
sortByNorelevance (default) or date_posted.
keywordYesSearch keyword or phrase, e.g. 'we are hiring data engineers'.
datePostedNoDate window such as 'past-24h', 'past-week' or 'past-month'.
authorTitleNoKeyword in the author's title, e.g. 'talent acquisition'.
contentTypeNoOptional content type filter (e.g. 'videos', 'images', 'jobs').
fromCompanyIdsNoOnly posts by these company pages.
authorCompanyIdsNoNumeric company ids of the author's employer.
authorIndustryIdsNo
fromMemberUsernamesNoOnly posts by these member usernames.
mentionsMemberUsernamesNo
mentionsOrganizationIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 beyond that by disclosing that only public posts are searched, what the response contains (post text, author, engagement counts, urn/url), and that results are paged.

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 definition is one front-loaded sentence that leads with the core purpose and then enumerates filters compactly, followed by a short return/paging clause. The dense filter list is efficient, though it reads as a comma run rather than clearly grouped and could be slightly easier to scan.

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 13-parameter search tool with no output schema, the description covers purpose, filter scope, return fields and paging, which is close to everything an agent needs to invoke it correctly. Remaining gaps (page-size interaction with the provider's page limit, content-type filtering) are minor and partly handled by schema descriptions.

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 77%, and the description compensates for the gaps by naming filters that are undocumented in the schema, notably author industry ids and mentions (member usernames / organization ids). It also gives concrete date-window examples ('past-24h', 'past-week', 'past-month') and restates the relevance/date_posted sort choice.

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?

The description opens with a specific verb+resource ("Search public posts by keyword") and scopes it to public posts, so the agent knows exactly what is retrieved. It does not name a sibling like employee_search_posts_by_hashtag to differentiate, but the keyword-based search scope is unambiguous on its own.

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?

Usage is implied by the keyword-search framing and the enumerated filters (author title, company ids, mentions), which suggests when this tool fits. However, there is no explicit guidance on when to prefer this over employee_search_posts_by_hashtag or employee_profile_posts, and no stated prerequisites or 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