Skip to main content
Glama

run_owler_companies_news

Fetch recent Owler company news by slug or URL, returning titles, summaries, publishers, dates, and links for monitoring or research.

Instructions

Latest news about one Owler company (slug or URL): title, summary, publisher, date and link. 1 point per returned record.

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": {
      "company": "<company>"
    },
    "name": "run_owler_companies_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany slug or Owler URL. e.g. stripe
max_itemsNoMax items (up to 10)
news_typeNoNews type. Options: all = All (latest 10), news = News (latest 3), blog = Blog (latest 3), videos = Videos (latest 3), press = Press releases (latest 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return fields and a genuinely useful cost model ('1 point per returned record'), which helps the agent reason about max_items. However, it says nothing about authentication, rate limits, or whether results can be paginated beyond the schema's cap.

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 tight sentences with the core purpose front-loaded and the return shape plus cost trailing. No filler and every clause carries 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?

No output schema exists, but the description compensates by listing the returned fields (title, summary, publisher, date, link) and the cost. For a low-complexity list tool with fully documented parameters, this is nearly sufficient; only usage context and any pagination behavior are missing.

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 coverage is 100%, so all three parameters are already documented, including the slug/URL format and the enum values for news_type. The description adds the per-record cost signal but no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 names a specific verb+resource combination ('Latest news about one Owler company') and enumerates the returned fields. It is clearly distinct from siblings like run_owler_companies and run_owler_companies_competitors, though it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when/when-not guidance and no named alternatives. The phrase 'one Owler company' implies single-company scope, but the agent is left to infer when this news tool is preferable to the sibling company or competitor tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools