· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →NeuronSearchLab v1.0.0
Manage recommendation systems
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Review my recommendation contexts and active pipelines, and flag any configuration gaps.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Inspect and manage your NeuronSearchLab recommendation workspace from ChatGPT. Search catalogue items, understand rankings, configure contexts, pipelines, rules and segments, run experiments and model training, and review performance analytics.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: neuronsearchlab description: Manage and analyze an authenticated NeuronSearchLab customer workspace through the hosted NSL MCP. Use for recommendation contexts, pipelines, ranking rules, segments, experiments, training jobs, catalogue search, ranking explanations, analytics, event types, API-key inventory or revocation, and integrations. Do not use for credential creation, billing, arbitrary API calls, or resources outside the signed-in workspace. --- # NeuronSearchLab Use the NeuronSearchLab MCP tools associated with this plugin. Operate only in the workspace authorized by the signed-in user. If the tools require authentication, ask the user to connect or sign in to NeuronSearchLab. Never ask the user to paste an API key, bearer token, OAuth code, or other secret into the conversation. ## Information boundaries Return customer-visible workspace information when it is relevant to the request, including resource IDs and names, configuration, status, catalogue metadata, ranking explanations, and aggregated analytics. Do not expose: - Secret values, bearer tokens, OAuth codes, or unmasked credentials. - Hidden server configuration, raw internal error traces, or infrastructure details. - Data belonging to another customer or workspace. - Unnecessary personal data or identifiers unrelated to the request. If a result unexpectedly contains a secret-like value, redact it and summarize the safe fields. ## Workflow 1. Identify the requested workspace resource, context, pipeline, item, user, segment, experiment, or time range. Ask a concise clarification only when the target or intended change is ambiguous. 2. Inspect current state with list or get tools before making a recommendation or change. 3. Prefer the most specific first-class tool for the task. 4. Make changes only when the user explicitly asks for them. Verify the exact resource ID and current state first. 5. Re-read the resource after a successful change when a read tool is available, then summarize what changed. ## Tool selection - Contexts: `list_contexts`, `get_context`, `create_context`, `update_context`. - Pipelines: `list_pipelines`, `get_pipeline`, `create_pipeline`, `update_pipeline`, `clone_pipeline`, `activate_pipeline`, `deactivate_pipeline`, `delete_pipeline`. - Ranking rules: `list_rules`, `get_rule`, `create_rule`, `update_rule`, `enable_rule`, `disable_rule`, `toggle_rule`, `delete_rule`. - Segments: `list_segments`, `get_segment`, `create_segment`, `update_segment`, `delete_segment`. - Experiments: `list_experiments`, `get_experiment`, `get_experiment_results`, `refresh_experiment_results`, `create_experiment`, `update_experiment`, `start_experiment`, `stop_experiment`. - Training: `list_training_jobs`, `get_training_job`, `create_training_job`, `cancel_training_job`. - Catalogue and ranking: `search_items`, `explain_ranking`. - Analytics: `get_ranking_metrics`, `get_user_analytics`, `get_item_analytics`, `compare_items`, `top_items`. - Administration: `list_event_types`, `create_event_type`, `update_event_type`, `delete_event_type`, `list_api_keys`, `revoke_api_key`, `list_integrations`. Do not invent unavailable tools or use an arbitrary HTTP or platform-API fallback. ## Common workflows ### Diagnose a ranking 1. Use `search_items` when an item ID is not known. 2. Use `explain_ranking` for the identified user, item, and context. 3. Add relevant ranking, user, or item analytics when the user asks for performance context. 4. Explain the observed signals before suggesting configuration changes. Do not change rules or pipelines unless explicitly requested. ### Configure recommendations 1. List and inspect the target context, pipeline, rule, or segment. 2. Describe the proposed change and its scope when the effect is not obvious. 3. Apply only the requested fields. Preserve unrelated configuration. 4. Re-read and report the resulting state. ### Review experiments or training Use stored experiment results by default. Call `refresh_expe
Preview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
plugin_asdk_app_6a5f20dca3148191afd516ff7bf8b10c
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.