Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

listReviews

Read-onlyIdempotent

Retrieve review records page by page for moderation queues, exports, and review-velocity reports. Filter by status or keyword, sort results, and opt into full review text when needed.

Instructions

List reviews - Paginated enumeration of review records. Read-only.

Lean by default: review_description is truncated to the first 500 chars + when longer. Truncated rows are tagged review_description_truncated: true. Pass include_full_text=1 to restore the full body per call (use sparingly at high limit — review text is unbounded and can dominate payload).

Use when: building moderation queues (filter review_status=0 for Pending), exporting all reviews, running review-velocity reports, or paginating through every review on the site. For keyword-in-body matching, use property=review_description property_operator=LIKE property_value=<word>. For a single known review use getReview.

Pagination: cursor-based (limit, page). See Rule: Pagination for full cursor/cap/stop semantics.

Filter/sort: property+property_value+property_operator, order_column+order_type. See Rule: Filter operators for the verified-working operator set, silent-drop detection, and derived-field unfilterability.

Enums: property_operator: =, LIKE, >, <, >=, <=.

See also: getReview (single record by ID).

Returns: { status: "success", total, current_page, total_pages, next_page, prev_page, message: [...records] }. Each record is the full resource object (with review_description truncated by default; see Rule: Lean read responses).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPagination cursor (use next_page from previous response)
limitNoRecords per page (default 25, max 100)
propertyNoColumn key to filter by (present on the response rows; a wrong name silently returns empty). For multi-condition AND, pass parallel arrays here and in `property_value`/`property_operator` — equal length, Nth entries paired. See Rule: Compound filters.
order_typeNoSort direction: ASC or DESC
order_columnNoColumn to sort by — a column key present on the response rows (a wrong name silently returns empty)
property_valueNoValue to filter by; array to pair with a `property` array (same length).
include_full_textNoOpt in to return the full `review_description` body. Default is lean: bodies over 500 chars are truncated and tagged `review_description_truncated: true`. Set `1` when the agent needs full text (single-record inspection, exporting, keyword-in-body analysis).
property_operatorNoFilter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. Array to pair with a `property` array (same length). See Rule: Filter operators for value shapes.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv6.58.3
    • changedInput schema / properties / property_value / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
  2. Changed1 schema field changedv6.58.2
    • changedInput schema / properties / property_value / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
  3. Changed10 schema fields changedv6.58.0
    • changedInput schema / properties / order_column / description
      Previous value: -"Column to sort by"New value: +"Column to sort by — a column key present on the response rows (a wrong name silently returns empty)"
    • addedInput schema / properties / property / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / property / description
      Previous value: -"Field name to filter by"New value: +"Column key to filter by (present on the response rows; a wrong name silently returns empty). For multi-condition AND, pass parallel arrays here and in `property_value`/`property_operator` — equal length, Nth entries paired. See Rule: Compound filters."
    • removedInput schema / properties / property / type
      Removed value: -"string"
    • addedInput schema / properties / property_operator / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / property_operator / description
      Previous value: -"Filter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. See Rule: Filter operators for value shapes."New value: +"Filter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. Array to pair with a `property` array (same length). See Rule: Filter operators for value shapes."
    • removedInput schema / properties / property_operator / type
      Removed value: -"string"
    • addedInput schema / properties / property_value / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / property_value / description
      Previous value: -"Value to filter by"New value: +"Value to filter by; array to pair with a `property` array (same length)."
    • removedInput schema / properties / property_value / type
      Removed value: -"string"
  4. Addedv6.55.39
  5. Removedv6.55.19
  6. Addedv6.49.4
  7. Removedv6.48.1
  8. Addedv6.0.19
  9. Removedv6.0.18
  10. Changed3 schema fields changedv6.0.14
    • changedInput schema / properties / include_full_text / default
      Previous value: -falseNew value: +0
    • addedInput schema / properties / include_full_text / enum
      Added value: +[
      +  0,
      +  1
      +]
    • changedInput schema / properties / include_full_text / type
      Previous value: -"boolean"New value: +"integer"
  11. Changed1 schema field changedv6.0.12
    • addedInput schema / properties / include_full_text
      Added value: +{
      +  "default": false,
      +  "description": "Opt in to return the full `review_description` body. Default is lean: bodies over 500 chars are truncated and tagged `review_description_truncated: true`. Set `1` when the agent needs full text (single-record inspection, exporting, keyword-in-body analysis).",
      +  "type": "boolean"
      +}
  12. Addedv6.0.7
  13. Removed
  14. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Description adds key behaviors: truncation of review_description, pagination cursor semantics, filter/sort rules, and performance considerations for include_full_text.

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?

Well-structured with clear sections and front-loaded purpose. Every sentence adds value without redundancy. Despite length, it remains scannable and informative.

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?

Covers all key aspects: pagination, filtering/sorting, truncation, return format, usage guidance, and performance considerations. No missing context for effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds rich semantics: explains lean default truncation, pagination cursor usage, compound filter arrays, operator enumerations, and performance note for include_full_text.

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?

Opens with 'List reviews - Paginated enumeration of review records. Read-only.' Clearly states verb (list), resource (reviews), and distinguishes from sibling getReview for single records.

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 lists use cases: moderation queues, exporting, reports, pagination. Specifies when to use getReview instead, and mentions keyword-in-body filtering approach.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brilliantdirectories/brilliant-directories-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server