Skip to main content
Glama

Search Jobsite articles

search_articles
Read-onlyIdempotent

Search Jobsite's published marketing content — blog articles, head-to-head COMPETITOR COMPARISON pages (e.g. 'Jobsite vs Procore', 'Jobsite vs SiteDocs', 'Jobsite vs SafetyCulture'), and pillar guides. Use this whenever the user asks how Jobsite compares to a competitor ('how are you better than Procore', 'Jobsite vs SafetyCulture', 'why pick you over X'), or asks for a published article on a construction-safety topic. Returns matching articles with a relevant excerpt and a link to the full page. This is DISTINCT from lookup_jobsite_docs (product how-to) and search_law_corpus (OSHA regulatory text). If nothing matches, say you don't have an article on it rather than inventing a comparison.

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": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles to return. Defaults to 4, cap 6.
queryYesNatural-language query, e.g. 'how is Jobsite better than Procore', 'Jobsite vs SiteDocs', 'confined space article'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (matching articles with a relevant excerpt and link to the full page) and an anti-hallucination instruction for the empty-result case. It stops short of describing ranking or relevance behavior, which keeps it off a 5.

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 the core purpose, then scope examples, then disambiguation, then return/fallback behavior — a sensible ordering. The competitor examples appear twice (parenthetical list and quoted user phrasings), which is mildly redundant, but each sentence still does routing work.

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?

For a two-parameter search tool with no output schema, the description covers what it searches, when to use it, what it returns, how it differs from neighbors, and what to do on no match. Nothing an agent needs in order to invoke it correctly is 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% and the schema itself supplies natural-language query examples and the limit default/cap, so the description carries no additional parameter burden. It does not restate or extend the meaning of 'query' or 'limit', which is acceptable given the baseline for fully documented schemas.

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?

States a specific verb and resource (search Jobsite's published marketing content) and enumerates the content types covered: blog articles, competitor comparison pages with named examples, and pillar guides. It explicitly separates itself from lookup_jobsite_docs and search_law_corpus, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete triggering conditions with sample user phrasings ('how are you better than Procore', 'Jobsite vs SafetyCulture') plus a second use case (published article on a construction-safety topic). It names the two sibling tools it is NOT and what they cover, and prescribes fallback behavior when nothing matches.

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