Skip to main content
Glama

search_newsletters

按快讯类型、标题/正文关键词和发布时间分页查询快讯、创投电报,默认按发布时间倒序;适合回答今天创投电报有哪些、最近24小时某赛道快讯、本周融资快讯汇总。快讯类型ID请用 get_lookup_options(lookup_type="newsletter_type") 获取;需要关联到公司或事件时在 fields 里加 main_body_type、main_body_id、item_id,main_body_type 为 1 时 main_body_id 是 company_id,为 2 时是 investor_id。

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

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
keywordNo
date_endNo
type_idsNo
page_sizeNo
date_startNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses default sort (publish time descending), pagination, and the non-obvious field-level semantics of main_body_type/main_body_id/item_id including the 1=company_id, 2=investor_id mapping. It says nothing about result caps, permissions, or query cost, but return shape is covered by the output schema.

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 capability and scope, then the lookup and field-mapping guidance, so an agent reading only the first clause already knows what the tool does. Dense but every sentence carries information; the single long semicolon-chained sentence is slightly harder to scan than a short bulleted form.

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 7-parameter, zero-annotation, read-only search tool with an existing output schema, the definition covers filtering, sorting, type resolution, and entity linking. The only material omission is how to continue pagination with the returned cursor.

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 0%, so the description must compensate and largely does: type_ids is tied to get_lookup_options, keyword is scoped to title/body, date_start/date_end are tied to publish time, and fields gets explicit entity-association semantics that the schema does not convey. The gap is cursor and page_size, whose pagination contract (opaque cursor, max page size) is never explained.

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 opens with a specific verb and resource (分页查询快讯、创投电报) and immediately enumerates the three filter facets (type, title/body keyword, publish time) plus the default sort order. The resource is distinct enough from the sibling set of company/investor/event searches that an agent can route to it without opening the schema.

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?

Three concrete question shapes are given ('today's VC telegraphs', 'last 24h news in a track', 'this week's funding roundup'), which tells the agent exactly what class of question this tool answers. It also routes to the sibling get_lookup_options for resolving type IDs. It stops short of stating when NOT to use it (e.g. versus search_events), so it is not a full 5.

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.