Skip to main content
Glama

list_saved_searches

Read-onlyIdempotent

Liste des recherches sauvegardées de l'utilisateur (page Actualités - Veille de l'app Insourcia).

Utiliser cet outil :

  • AVANT create_saved_search, pour vérifier qu'une veille équivalente n'existe pas déjà et éviter les doublons de nom.

  • Pour répondre à "quelles veilles ai-je ?" / "quelles sont mes recherches sauvegardées ?".

Réponse : { saved_searches: [{ id, name, filters (filtres normalisés stockés), result_count (nombre de sociétés matchant, null si indisponible), alert_enabled (alerte quotidienne nouvelles sociétés active ou non), url (page Actualités), created_at }], total }. Les recherches sont triées de la plus récente à la plus ancienne. Liste vide = aucune veille configurée.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNombre max de recherches retournées (défaut : 100)

Output Schema

NameRequiredDescriptionDefault
totalYes
saved_searchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / saved_searches / items / properties / watch_cap_left_out
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "properties": {
      +        "count": {
      +          "type": "number"
      +        },
      +        "date": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "count",
      +        "date"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Nombre max de recherches retournees (defaut 100)"New value: +"Nombre max de recherches retournées (défaut : 100)"
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "llm_model"
      -]
  4. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "llm_model"
      +]
  5. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "context"
      -]
  6. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  7. 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 read-only, idempotent, non-destructive, closed-world behavior, and the description adds ordering (newest first), the meaning of an empty list, and that result_count may be null when unavailable. The field-by-field return enumeration partly restates what the existing output schema already provides, so it stops short of 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-loads the one-line purpose, then uses a short bullet list for usage and a compact response summary. The response enumeration is the longest block and is largely duplicative of the output schema, but the rest is tight.

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 read-only listing tool with full annotation coverage and an output schema, everything an agent needs is present: when to call it, what it returns, sort order, and empty/null edge cases.

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?

There is a single optional 'limit' parameter with 100% schema description coverage, so the schema already carries its meaning (max results, default 100). The description never mentions pagination or limits, which is acceptable at this coverage level but adds nothing.

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 ('Liste des recherches sauvegardées de l'utilisateur') and pins the product context (page Actualités – Veille de l'app Insourcia), which separates it cleanly from create_saved_search and the company/news siblings.

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?

Explicitly prescribes when to call it ('AVANT create_saved_search' to check for duplicates) and which user questions it answers ('quelles veilles ai-je ?'), giving both a sequencing rule and an intent trigger with no inference required.

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